From: Joerg Roedel <joro@8bytes.org>
To: Rob Clark <robdclark@gmail.com>
Cc: "iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Sricharan R <sricharan@codeaurora.org>,
Will Deacon <will.deacon@arm.com>
Subject: Re: [pull] iommu: qcom_iommu for v4.14
Date: Tue, 15 Aug 2017 22:59:56 +0200 [thread overview]
Message-ID: <20170815205956.GL30515@8bytes.org> (raw)
In-Reply-To: <CAF6AEGtxmJUOKZpqMZfYkgP6Bs7mbGAzEtC8on8TkjdTU5pcFQ@mail.gmail.com>
On Tue, Aug 15, 2017 at 12:52:11PM -0400, Rob Clark wrote:
> On Tue, Aug 15, 2017 at 11:42 AM, Joerg Roedel <joro@8bytes.org> wrote:
> > On Sun, Aug 13, 2017 at 10:27:36AM -0400, Rob Clark wrote:
> >> Hi Joerg,
> >>
> >> These patches have been on list for quite some time now. The bindings
> >> have r-b from Rob Herring, and the patch touching arm-smmu has Will's
> >> a-b. And all the review comments on the driver patches have been
> >> addressed (despite no one stepping up w/ a r-b tag). Please consider
> >> merging this pull request for v4.14
> >
> > Okay, I applied it, not from this pull-request, but from your last
> > post. Some comments for the future below.
>
> Thanks. Patches from list are the same.
>
> For future reference to you prefer to pick up patches from list?
> (Dave prefers pull req's for drm, but I guess the volume of patches
> for an iommu driver should be lower.)
For now please send any patch for the qcom iommu directly to me (and Cc
relevant ML) and then I take care of them. Can you also add a
MAINTAINERS entry for it?
Regards,
Joerg
prev parent reply other threads:[~2017-08-15 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 14:27 [pull] iommu: qcom_iommu for v4.14 Rob Clark
2017-08-13 14:29 ` Rob Clark
[not found] ` <CAF6AEGuNqQtJBhLAFu3NdUAjKJrVvR9WtHL-eCRN0H1Di6_4mQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-15 15:42 ` Joerg Roedel
2017-08-15 16:52 ` Rob Clark
2017-08-15 20:59 ` 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=20170815205956.GL30515@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=sricharan@codeaurora.org \
--cc=will.deacon@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;
as well as URLs for NNTP newsgroup(s).