All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Rob Clark <robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-arm-msm
	<linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
	<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Subject: Re: [pull] iommu: qcom_iommu for v4.14
Date: Tue, 15 Aug 2017 17:42:33 +0200	[thread overview]
Message-ID: <20170815154232.GB25618@8bytes.org> (raw)
In-Reply-To: <CAF6AEGuNqQtJBhLAFu3NdUAjKJrVvR9WtHL-eCRN0H1Di6_4mQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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.

> Rob Clark (3):
>       Docs: dt: document qcom iommu bindings

This patch has no commit-message. Usually that is a reason for me to
reject the patch. I applied it anyway this time because it has an
Reviewed-By from a device-tree maintainer, and if its fine for him, I
can live with it.

For the other three patches I edited the Subject line to match the
convention of the iommu-tree, which is "iommu/<driver>: _Capital Letter_...

The patches below are now named:

>       iommu: arm-smmu: split out register defines
        iommu/arm-smmu: Split out register defines

>       iommu: add qcom_iommu
        iommu/qcom: Add qcom_iommu
> 
> Stanimir Varbanov (1):
>       iommu: qcom: initialize secure page table
        iommu/qcom: Initialize secure page table

Please follow that convention for future patches.


Thanks,

	Joerg

  parent reply	other threads:[~2017-08-15 15:42 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 [this message]
2017-08-15 16:52     ` Rob Clark
2017-08-15 20:59       ` Joerg Roedel

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=20170815154232.GB25618@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=will.deacon-5wv7dgnIgG8@public.gmane.org \
    /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.