* [PATCH] MAINTAINERS: use the iommu list for the dma-mapping subsystem
@ 2017-08-26 9:27 Christoph Hellwig
2017-09-01 7:50 ` Christoph Hellwig
0 siblings, 1 reply; 5+ messages in thread
From: Christoph Hellwig @ 2017-08-26 9:27 UTC (permalink / raw)
To: linux-kernel, iommu; +Cc: m.szyprowski, robin.murphy
Maintaining a subsystem with linux-kernel as the main list is painful
as it has way to much traffic. On the other hand the dma-mapping
subsystem is small enough that a list on its own would be silly.
So use the list for the closes subsystem instead instead.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6f7721d1634c..1df11ed346a7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4175,7 +4175,7 @@ DMA MAPPING HELPERS
M: Christoph Hellwig <hch@lst.de>
M: Marek Szyprowski <m.szyprowski@samsung.com>
R: Robin Murphy <robin.murphy@arm.com>
-L: linux-kernel@vger.kernel.org
+L: iommu@lists.linux-foundation.org
T: git git://git.infradead.org/users/hch/dma-mapping.git
W: http://git.infradead.org/users/hch/dma-mapping.git
S: Supported
--
2.11.0
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH] MAINTAINERS: use the iommu list for the dma-mapping subsystem
2017-08-26 9:27 [PATCH] MAINTAINERS: use the iommu list for the dma-mapping subsystem Christoph Hellwig
@ 2017-09-01 7:50 ` Christoph Hellwig
2017-09-01 7:56 ` Marek Szyprowski
0 siblings, 1 reply; 5+ messages in thread
From: Christoph Hellwig @ 2017-09-01 7:50 UTC (permalink / raw)
To: linux-kernel, iommu; +Cc: Marek Szyprowski, Robin Murphy
Any comments? I'd like to add this to the 4.14 pull request.
On Sat, Aug 26, 2017 at 11:27:34AM +0200, Christoph Hellwig wrote:
> Maintaining a subsystem with linux-kernel as the main list is painful
> as it has way to much traffic. On the other hand the dma-mapping
> subsystem is small enough that a list on its own would be silly.
> So use the list for the closes subsystem instead instead.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 6f7721d1634c..1df11ed346a7 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4175,7 +4175,7 @@ DMA MAPPING HELPERS
> M: Christoph Hellwig <hch@lst.de>
> M: Marek Szyprowski <m.szyprowski@samsung.com>
> R: Robin Murphy <robin.murphy@arm.com>
> -L: linux-kernel@vger.kernel.org
> +L: iommu@lists.linux-foundation.org
> T: git git://git.infradead.org/users/hch/dma-mapping.git
> W: http://git.infradead.org/users/hch/dma-mapping.git
> S: Supported
> --
> 2.11.0
>
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
---end quoted text---
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] MAINTAINERS: use the iommu list for the dma-mapping subsystem
2017-09-01 7:50 ` Christoph Hellwig
@ 2017-09-01 7:56 ` Marek Szyprowski
2017-09-01 9:48 ` Robin Murphy
0 siblings, 1 reply; 5+ messages in thread
From: Marek Szyprowski @ 2017-09-01 7:56 UTC (permalink / raw)
To: Christoph Hellwig, linux-kernel, iommu; +Cc: Robin Murphy
Hi Christoph,
On 2017-09-01 09:50, Christoph Hellwig wrote:
> Any comments? I'd like to add this to the 4.14 pull request.
>
> On Sat, Aug 26, 2017 at 11:27:34AM +0200, Christoph Hellwig wrote:
>> Maintaining a subsystem with linux-kernel as the main list is painful
>> as it has way to much traffic. On the other hand the dma-mapping
>> subsystem is small enough that a list on its own would be silly.
>> So use the list for the closes subsystem instead instead.
>>
>> Signed-off-by: Christoph Hellwig <hch@lst.de>
Like I already said, its fine for me.
Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
>> ---
>> MAINTAINERS | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 6f7721d1634c..1df11ed346a7 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -4175,7 +4175,7 @@ DMA MAPPING HELPERS
>> M: Christoph Hellwig <hch@lst.de>
>> M: Marek Szyprowski <m.szyprowski@samsung.com>
>> R: Robin Murphy <robin.murphy@arm.com>
>> -L: linux-kernel@vger.kernel.org
>> +L: iommu@lists.linux-foundation.org
>> T: git git://git.infradead.org/users/hch/dma-mapping.git
>> W: http://git.infradead.org/users/hch/dma-mapping.git
>> S: Supported
>> --
>> 2.11.0
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] MAINTAINERS: use the iommu list for the dma-mapping subsystem
2017-09-01 7:56 ` Marek Szyprowski
@ 2017-09-01 9:48 ` Robin Murphy
2017-09-01 9:57 ` Joerg Roedel
0 siblings, 1 reply; 5+ messages in thread
From: Robin Murphy @ 2017-09-01 9:48 UTC (permalink / raw)
To: Christoph Hellwig, Joerg Roedel, Alex Williamson
Cc: Marek Szyprowski, linux-kernel, iommu
On 01/09/17 08:56, Marek Szyprowski wrote:
> Hi Christoph,
>
> On 2017-09-01 09:50, Christoph Hellwig wrote:
>> Any comments? I'd like to add this to the 4.14 pull request.
>>
>> On Sat, Aug 26, 2017 at 11:27:34AM +0200, Christoph Hellwig wrote:
>>> Maintaining a subsystem with linux-kernel as the main list is painful
>>> as it has way to much traffic. On the other hand the dma-mapping
>>> subsystem is small enough that a list on its own would be silly.
>>> So use the list for the closes subsystem instead instead.
>>>
>>> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Like I already said, its fine for me.
> Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
Fine by me too.
Joerg, Alex, are you OK with the odd bit of extra ML traffic?
Thanks,
Robin.
>>> ---
>>> MAINTAINERS | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 6f7721d1634c..1df11ed346a7 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -4175,7 +4175,7 @@ DMA MAPPING HELPERS
>>> M: Christoph Hellwig <hch@lst.de>
>>> M: Marek Szyprowski <m.szyprowski@samsung.com>
>>> R: Robin Murphy <robin.murphy@arm.com>
>>> -L: linux-kernel@vger.kernel.org
>>> +L: iommu@lists.linux-foundation.org
>>> T: git git://git.infradead.org/users/hch/dma-mapping.git
>>> W: http://git.infradead.org/users/hch/dma-mapping.git
>>> S: Supported
>>> --
>>> 2.11.0
>
> Best regards
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] MAINTAINERS: use the iommu list for the dma-mapping subsystem
2017-09-01 9:48 ` Robin Murphy
@ 2017-09-01 9:57 ` Joerg Roedel
0 siblings, 0 replies; 5+ messages in thread
From: Joerg Roedel @ 2017-09-01 9:57 UTC (permalink / raw)
To: Robin Murphy
Cc: Christoph Hellwig, Alex Williamson, Marek Szyprowski,
linux-kernel, iommu
On Fri, Sep 01, 2017 at 10:48:50AM +0100, Robin Murphy wrote:
> On 01/09/17 08:56, Marek Szyprowski wrote:
> > Hi Christoph,
> >
> > On 2017-09-01 09:50, Christoph Hellwig wrote:
> >> Any comments? I'd like to add this to the 4.14 pull request.
> >>
> >> On Sat, Aug 26, 2017 at 11:27:34AM +0200, Christoph Hellwig wrote:
> >>> Maintaining a subsystem with linux-kernel as the main list is painful
> >>> as it has way to much traffic. On the other hand the dma-mapping
> >>> subsystem is small enough that a list on its own would be silly.
> >>> So use the list for the closes subsystem instead instead.
> >>>
> >>> Signed-off-by: Christoph Hellwig <hch@lst.de>
> >
> > Like I already said, its fine for me.
> > Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
>
> Fine by me too.
>
> Joerg, Alex, are you OK with the odd bit of extra ML traffic?
Fine by me, of course.
Acked-by: Joerg Roedel <jroedel@suse.de>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-09-01 9:57 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-26 9:27 [PATCH] MAINTAINERS: use the iommu list for the dma-mapping subsystem Christoph Hellwig
2017-09-01 7:50 ` Christoph Hellwig
2017-09-01 7:56 ` Marek Szyprowski
2017-09-01 9:48 ` Robin Murphy
2017-09-01 9:57 ` Joerg Roedel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox