From: Joerg Roedel <joro@8bytes.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Christoph Hellwig <hch@lst.de>,
Alex Williamson <alex.williamson@redhat.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: Re: [PATCH] MAINTAINERS: use the iommu list for the dma-mapping subsystem
Date: Fri, 1 Sep 2017 11:57:54 +0200 [thread overview]
Message-ID: <20170901095754.42pevlr7cqaahqxh@8bytes.org> (raw)
In-Reply-To: <5b7d88b3-001e-7413-7bf3-789c234f7fdd@arm.com>
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>
prev parent reply other threads:[~2017-09-01 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=20170901095754.42pevlr7cqaahqxh@8bytes.org \
--to=joro@8bytes.org \
--cc=alex.williamson@redhat.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox