SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/04] ARM: shmobile: IPMMU compat string SoC part number update
Date: Tue, 15 Dec 2015 09:17:50 +0000	[thread overview]
Message-ID: <20151215091746.GA9915@verge.net.au> (raw)
In-Reply-To: <20151117043047.4521.84234.sendpatchset@little-apple>

On Tue, Nov 24, 2015 at 11:45:41AM +0900, Simon Horman wrote:
> On Tue, Nov 17, 2015 at 01:30:47PM +0900, Magnus Damm wrote:
> > ARM: shmobile: IPMMU compat string SoC part number update
> > 
> > [PATCH 01/04] ARM: shmobile: r8a7790: IPMMU compat string SoC part number update
> > [PATCH 02/04] ARM: shmobile: r8a7791: IPMMU compat string SoC part number update
> > [PATCH 03/04] ARM: shmobile: r8a7793: IPMMU compat string SoC part number update
> > [PATCH 04/04] ARM: shmobile: r8a7794: IPMMU compat string SoC part number update
> > 
> > Update R-Car Gen2 DT compat strings for IPMMU devices to follow the updated
> > DT binding documentation included in:
> > "[PATCH v2] iommu/ipmmu-vmsa: Include SoC part number in DT binding docs"
> > 
> > With this compat string change we may in the future add SoC-specific features
> > such as IPMMU performance counters that only exist on some SoCs.
> > 
> > Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> 
> I have marked these patches as deferred pending the binding changes being
> accepted. Please repost or otherwise ping me once that has happened.

As discussed elsewhere, the bindings have been accepted.
I have queued up these patches accordingly.

  parent reply	other threads:[~2015-12-15  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17  4:30 [PATCH 00/04] ARM: shmobile: IPMMU compat string SoC part number update Magnus Damm
2015-11-24  2:45 ` Simon Horman
2015-12-15  9:17 ` Simon Horman [this message]
2015-12-15  9:22 ` Magnus Damm

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=20151215091746.GA9915@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-sh@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox