From: Christoph Hellwig <hch@lst.de>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
"Pawel Osciak" <pawel@osciak.com>,
"Russell King" <linux@armlinux.org.uk>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
"Kyungmin Park" <kyungmin.park@samsung.com>,
linux-media@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
"Christoph Hellwig" <hch@lst.de>,
linux-arm-kernel@lists.infradead.org,
"Marek Szyprowski" <m.szyprowski@samsung.com>
Subject: Re: [PATCH 3/3] videobuf2: replace a layering violation with dma_map_resource
Date: Mon, 14 Jan 2019 12:12:13 +0100 [thread overview]
Message-ID: <20190114111213.GA31455@lst.de> (raw)
In-Reply-To: <20190114090456.03071201@coco.lan>
On Mon, Jan 14, 2019 at 09:04:56AM -0200, Mauro Carvalho Chehab wrote:
> It would be good if you could later send us a stable branch where
> you merged, in order to allow us to run some tests with the new
> DMA mapping patchset and be sure that it won't cause regressions
> to videobuf2.
I can do that, but the series as sent should be testable, results
welcome!
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
"Pawel Osciak" <pawel@osciak.com>,
"Russell King" <linux@armlinux.org.uk>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
"Kyungmin Park" <kyungmin.park@samsung.com>,
linux-media@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
"Christoph Hellwig" <hch@lst.de>,
linux-arm-kernel@lists.infradead.org,
"Marek Szyprowski" <m.szyprowski@samsung.com>
Subject: Re: [PATCH 3/3] videobuf2: replace a layering violation with dma_map_resource
Date: Mon, 14 Jan 2019 12:12:13 +0100 [thread overview]
Message-ID: <20190114111213.GA31455@lst.de> (raw)
In-Reply-To: <20190114090456.03071201@coco.lan>
On Mon, Jan 14, 2019 at 09:04:56AM -0200, Mauro Carvalho Chehab wrote:
> It would be good if you could later send us a stable branch where
> you merged, in order to allow us to run some tests with the new
> DMA mapping patchset and be sure that it won't cause regressions
> to videobuf2.
I can do that, but the series as sent should be testable, results
welcome!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: "Christoph Hellwig" <hch@lst.de>,
"Pawel Osciak" <pawel@osciak.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
"Russell King" <linux@armlinux.org.uk>,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] videobuf2: replace a layering violation with dma_map_resource
Date: Mon, 14 Jan 2019 12:12:13 +0100 [thread overview]
Message-ID: <20190114111213.GA31455@lst.de> (raw)
In-Reply-To: <20190114090456.03071201@coco.lan>
On Mon, Jan 14, 2019 at 09:04:56AM -0200, Mauro Carvalho Chehab wrote:
> It would be good if you could later send us a stable branch where
> you merged, in order to allow us to run some tests with the new
> DMA mapping patchset and be sure that it won't cause regressions
> to videobuf2.
I can do that, but the series as sent should be testable, results
welcome!
next prev parent reply other threads:[~2019-01-14 11:12 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190111181841epcas3p2d7c0bf8f5c11a9863e22ec1b12da6e1b@epcas3p2.samsung.com>
2019-01-11 18:17 ` fix a layering violation in videobuf2 and improve dma_map_resource Christoph Hellwig
2019-01-11 18:17 ` Christoph Hellwig
2019-01-11 18:17 ` Christoph Hellwig
2019-01-11 18:17 ` [PATCH 1/3] dma-mapping: remove the default map_resource implementation Christoph Hellwig
2019-01-11 18:17 ` Christoph Hellwig
2019-01-11 18:17 ` Christoph Hellwig
2019-01-14 13:12 ` Robin Murphy
2019-01-14 13:12 ` Robin Murphy
2019-01-14 17:08 ` Christoph Hellwig
2019-01-14 17:08 ` Christoph Hellwig
2019-01-14 17:08 ` Christoph Hellwig
2019-01-11 18:17 ` [PATCH 2/3] dma-mapping: don't BUG when calling dma_map_resource on RAM Christoph Hellwig
2019-01-11 18:17 ` Christoph Hellwig
2019-01-11 18:17 ` Christoph Hellwig
2019-01-14 14:16 ` Robin Murphy
2019-01-14 14:16 ` Robin Murphy
2019-01-11 18:17 ` [PATCH 3/3] videobuf2: replace a layering violation with dma_map_resource Christoph Hellwig
2019-01-11 18:17 ` Christoph Hellwig
2019-01-11 18:17 ` Christoph Hellwig
2019-01-11 19:54 ` Mauro Carvalho Chehab
2019-01-11 19:54 ` Mauro Carvalho Chehab
2019-01-11 19:54 ` Mauro Carvalho Chehab
2019-01-14 10:31 ` Christoph Hellwig
2019-01-14 10:31 ` Christoph Hellwig
2019-01-14 10:31 ` Christoph Hellwig
2019-01-14 11:04 ` Mauro Carvalho Chehab
2019-01-14 11:04 ` Mauro Carvalho Chehab
2019-01-14 11:04 ` Mauro Carvalho Chehab
2019-01-14 11:12 ` Christoph Hellwig [this message]
2019-01-14 11:12 ` Christoph Hellwig
2019-01-14 11:12 ` Christoph Hellwig
2019-01-14 12:42 ` Marek Szyprowski
2019-01-14 12:42 ` Marek Szyprowski
2019-01-14 12:42 ` Marek Szyprowski
2019-01-17 17:21 ` Christoph Hellwig
2019-01-17 17:21 ` Christoph Hellwig
2019-01-17 17:21 ` Christoph Hellwig
2019-01-18 9:41 ` Marek Szyprowski
2019-01-18 9:41 ` Marek Szyprowski
2019-01-18 9:41 ` Marek Szyprowski
2019-01-31 15:31 ` Christoph Hellwig
2019-01-31 15:31 ` Christoph Hellwig
2019-01-31 15:31 ` Christoph Hellwig
2019-01-14 11:43 ` fix a layering violation in videobuf2 and improve dma_map_resource Marek Szyprowski
2019-01-14 11:43 ` Marek Szyprowski
2019-01-14 11:43 ` Marek Szyprowski
2019-01-18 11:37 fix a layering violation in videobuf2 and improve dma_map_resource v2 Christoph Hellwig
2019-01-18 11:37 ` [PATCH 3/3] videobuf2: replace a layering violation with dma_map_resource Christoph Hellwig
2019-01-18 11:37 ` Christoph Hellwig
2019-01-18 11:37 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190114111213.GA31455@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab+samsung@kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=pawel@osciak.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.