Message ID | 20170620124140.GA27163@lst.de (mailing list archive) |
---|---|
State | Not Applicable |
Headers | show |
Hi Christoph, On Tue, 20 Jun 2017 14:41:40 +0200 Christoph Hellwig <hch@lst.de> wrote: > > On Fri, Jun 16, 2017 at 08:10:15PM +0200, Christoph Hellwig wrote: > > I plan to create a new dma-mapping tree to collect all this work. > > Any volunteers for co-maintainers, especially from the iommu gang? > > Ok, I've created the new tree: > > git://git.infradead.org/users/hch/dma-mapping.git for-next > > Gitweb: > > http://git.infradead.org/users/hch/dma-mapping.git/shortlog/refs/heads/for-next > > And below is the patch to add the MAINTAINERS entry, additions welcome. > > Stephen, can you add this to linux-next? Added from tomorrow. I have another tree called dma-mapping: git://git.linaro.org/people/mszyprowski/linux-dma-mapping.git#dma-mapping-next Contacts: Marek Szyprowski and Kyungmin Park (cc'd) I have called your tree dma-mapping-hch for now. The other tree has not been updated since 4.9-rc1 and I am not sure how general it is. Marek, Kyungmin, any comments? Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window. You will need to ensure that the patches/commits in your tree/series have been: * submitted under GPL v2 (or later) and include the Contributor's Signed-off-by, * posted to the relevant mailing list, * reviewed by you (or another maintainer of your subsystem tree), * successfully unit tested, and * destined for the current or next Linux merge window. Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.
Hi Christoph, On 20/06/17 13:41, Christoph Hellwig wrote: > On Fri, Jun 16, 2017 at 08:10:15PM +0200, Christoph Hellwig wrote: >> I plan to create a new dma-mapping tree to collect all this work. >> Any volunteers for co-maintainers, especially from the iommu gang? > > Ok, I've created the new tree: > > git://git.infradead.org/users/hch/dma-mapping.git for-next > > Gitweb: > > http://git.infradead.org/users/hch/dma-mapping.git/shortlog/refs/heads/for-next > > And below is the patch to add the MAINTAINERS entry, additions welcome. I'm happy to be a reviewer, since I've been working in this area for some time, particularly with the dma-iommu code and arm64 DMA ops. Robin. > Stephen, can you add this to linux-next? > > --- > From 335979c41912e6c101a20b719862b2d837370df1 Mon Sep 17 00:00:00 2001 > From: Christoph Hellwig <hch@lst.de> > Date: Tue, 20 Jun 2017 11:17:30 +0200 > Subject: MAINTAINERS: add entry for dma mapping helpers > > This code has been spread between getting in through arch trees, the iommu > tree, -mm and the drivers tree. There will be a lot of work in this area, > including consolidating various arch implementations into more common > code, so ensure we have a proper git tree that facilitates cooperation with > the architecture maintainers. > > Signed-off-by: Christoph Hellwig <hch@lst.de> > --- > MAINTAINERS | 13 +++++++++++++ > 1 file changed, 13 insertions(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 09b5ab6a8a5c..56859d53a424 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -2595,6 +2595,19 @@ S: Maintained > F: net/bluetooth/ > F: include/net/bluetooth/ > > +DMA MAPPING HELPERS > +M: Christoph Hellwig <hch@lst.de> > +L: linux-kernel@vger.kernel.org > +T: git git://git.infradead.org/users/hch/dma-mapping.git > +W: http://git.infradead.org/users/hch/dma-mapping.git > +S: Supported > +F: lib/dma-debug.c > +F: lib/dma-noop.c > +F: lib/dma-virt.c > +F: drivers/base/dma-mapping.c > +F: drivers/base/dma-coherent.c > +F: include/linux/dma-mapping.h > + > BONDING DRIVER > M: Jay Vosburgh <j.vosburgh@gmail.com> > M: Veaceslav Falico <vfalico@gmail.com> > -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Jun 20, 2017 at 02:14:36PM +0100, Robin Murphy wrote: > Hi Christoph, > > On 20/06/17 13:41, Christoph Hellwig wrote: > > On Fri, Jun 16, 2017 at 08:10:15PM +0200, Christoph Hellwig wrote: > >> I plan to create a new dma-mapping tree to collect all this work. > >> Any volunteers for co-maintainers, especially from the iommu gang? > > > > Ok, I've created the new tree: > > > > git://git.infradead.org/users/hch/dma-mapping.git for-next > > > > Gitweb: > > > > http://git.infradead.org/users/hch/dma-mapping.git/shortlog/refs/heads/for-next > > > > And below is the patch to add the MAINTAINERS entry, additions welcome. > > I'm happy to be a reviewer, since I've been working in this area for > some time, particularly with the dma-iommu code and arm64 DMA ops. Great, I'll add you! -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Jun 20, 2017 at 11:04:00PM +1000, Stephen Rothwell wrote: > git://git.linaro.org/people/mszyprowski/linux-dma-mapping.git#dma-mapping-next > > Contacts: Marek Szyprowski and Kyungmin Park (cc'd) > > I have called your tree dma-mapping-hch for now. The other tree has > not been updated since 4.9-rc1 and I am not sure how general it is. > Marek, Kyungmin, any comments? I'd be happy to join efforts - co-maintainers and reviers are always welcome. -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Christoph, On 2017-06-20 15:16, Christoph Hellwig wrote: > On Tue, Jun 20, 2017 at 11:04:00PM +1000, Stephen Rothwell wrote: >> git://git.linaro.org/people/mszyprowski/linux-dma-mapping.git#dma-mapping-next >> >> Contacts: Marek Szyprowski and Kyungmin Park (cc'd) >> >> I have called your tree dma-mapping-hch for now. The other tree has >> not been updated since 4.9-rc1 and I am not sure how general it is. >> Marek, Kyungmin, any comments? > I'd be happy to join efforts - co-maintainers and reviers are always > welcome. I did some dma-mapping unification works in the past and my tree in linux-next was a side effect of that. I think that for now it can be dropped in favor of Christoph's tree. I can also do some review and help in maintainers work if needed, although I was recently busy with other stuff. Christoph: Could you add me to your MAINTAINERS patch, so further dma-mapping related patches hopefully will be also CC: to me? Best regards
Hi all, On Wed, 21 Jun 2017 15:32:39 +0200 Marek Szyprowski <m.szyprowski@samsung.com> wrote: > > On 2017-06-20 15:16, Christoph Hellwig wrote: > > On Tue, Jun 20, 2017 at 11:04:00PM +1000, Stephen Rothwell wrote: > >> git://git.linaro.org/people/mszyprowski/linux-dma-mapping.git#dma-mapping-next > >> > >> Contacts: Marek Szyprowski and Kyungmin Park (cc'd) > >> > >> I have called your tree dma-mapping-hch for now. The other tree has > >> not been updated since 4.9-rc1 and I am not sure how general it is. > >> Marek, Kyungmin, any comments? > > I'd be happy to join efforts - co-maintainers and reviers are always > > welcome. > > I did some dma-mapping unification works in the past and my tree in > linux-next > was a side effect of that. I think that for now it can be dropped in > favor of > Christoph's tree. I can also do some review and help in maintainers work if > needed, although I was recently busy with other stuff. OK, so I have dropped the dma-mapping tree and renamed dma-mapping-hch to dma-mapping.
On Wed, Jun 21, 2017 at 03:32:39PM +0200, Marek Szyprowski wrote: > linux-next > was a side effect of that. I think that for now it can be dropped in favor > of > Christoph's tree. I can also do some review and help in maintainers work if > needed, although I was recently busy with other stuff. > > Christoph: Could you add me to your MAINTAINERS patch, so further > dma-mapping > related patches hopefully will be also CC: to me? I've added you as a co-maintainer, thanks! -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/MAINTAINERS b/MAINTAINERS index 09b5ab6a8a5c..56859d53a424 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2595,6 +2595,19 @@ S: Maintained F: net/bluetooth/ F: include/net/bluetooth/ +DMA MAPPING HELPERS +M: Christoph Hellwig <hch@lst.de> +L: linux-kernel@vger.kernel.org +T: git git://git.infradead.org/users/hch/dma-mapping.git +W: http://git.infradead.org/users/hch/dma-mapping.git +S: Supported +F: lib/dma-debug.c +F: lib/dma-noop.c +F: lib/dma-virt.c +F: drivers/base/dma-mapping.c +F: drivers/base/dma-coherent.c +F: include/linux/dma-mapping.h + BONDING DRIVER M: Jay Vosburgh <j.vosburgh@gmail.com> M: Veaceslav Falico <vfalico@gmail.com>