devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: shh.xie@gmail.com
Cc: devicetree@vger.kernel.org, mark.rutland@arm.com,
	linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
	will.deacon@arm.com, shawnguo@kernel.org,
	linux-kernel@vger.kernel.org, arnd@arndb.de,
	Shaohui Xie <Shaohui.Xie@nxp.com>
Subject: Re: [PATCH 02/10][v3] dt-bindings: fsl: updates bindings for some SoC-specific devices
Date: Fri, 23 Sep 2016 08:22:35 -0500	[thread overview]
Message-ID: <20160923132235.GA15732@rob-hp-laptop> (raw)
In-Reply-To: <1473754203-22970-3-git-send-email-shh.xie@gmail.com>

On Tue, Sep 13, 2016 at 04:09:55PM +0800, shh.xie@gmail.com wrote:
> From: Shaohui Xie <Shaohui.Xie@nxp.com>

Again, subject could still be more specific. Aim to make it unique 
enough that the same subject could never appear again.
 
> SCFG and DCFG are SoC-specific devices can be found on SoCs like LS1021A,
> LS1043A and LS1046A, this patch updates bindings for SCFG and DCFG to
> reflect more SoCs.
> 
> Signed-off-by: Shaohui Xie <Shaohui.Xie@nxp.com>
> ---
> changes in V3:
> 1. added supported <chip>s.
> 
> change in V2:
> 1. new patch.
> 
>  Documentation/devicetree/bindings/arm/fsl.txt | 14 +++++++++++---
>  1 file changed, 11 insertions(+), 3 deletions(-)

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2016-09-23 13:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13  8:09 [PATCH 00/10] [v3] arm64: dts: add QorIQ LS1046A SoC and boards support shh.xie
2016-09-13  8:09 ` [PATCH 01/10] [v3] dt-bindings: fsl: update for more SoCs shh.xie
     [not found]   ` <1473754203-22970-2-git-send-email-shh.xie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-23 13:19     ` Rob Herring
2016-09-13  8:09 ` [PATCH 02/10][v3] dt-bindings: fsl: updates bindings for some SoC-specific devices shh.xie
2016-09-23 13:22   ` Rob Herring [this message]
2016-09-13  8:09 ` [PATCH 03/10][v3] dt-bindings: i2c: adds two more nxp devices shh.xie
2016-09-13  8:09 ` [PATCH 04/10] [v3] dt-bindings: qoriq-clock: update for more SoCs shh.xie
2016-09-23 13:23   ` Rob Herring
2016-09-13  8:09 ` [PATCH 05/10][v3] dt-bindings: ahci-fsl-qoriq: updated for SoC ls1046a shh.xie
2016-09-23 13:27   ` Rob Herring
2016-09-13  8:09 ` [PATCH 06/10] [v3] arm64: dts: add QorIQ LS1046A SoC support shh.xie
2016-09-13  8:10 ` [PATCH 07/10] [v3] Documentation: DT: Add entry for QorIQ LS1046A-RDB board shh.xie
2016-09-13  8:10 ` [PATCH 08/10] [v3] arm64: dts: add LS1046A-RDB board support shh.xie
     [not found] ` <1473754203-22970-1-git-send-email-shh.xie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-13  8:10   ` [PATCH 09/10] [v3] Documentation: DT: Add entry for QorIQ LS1046A-QDS board shh.xie-Re5JQEeQqe8AvxtiuMwx3w
2016-09-13  8:10   ` [PATCH 10/10] [v3] arm64: dts: add LS1046A-QDS board support shh.xie-Re5JQEeQqe8AvxtiuMwx3w
2016-10-21 13:38 ` [PATCH 00/10] [v3] arm64: dts: add QorIQ LS1046A SoC and boards support Shawn Guo

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=20160923132235.GA15732@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=Shaohui.Xie@nxp.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=shawnguo@kernel.org \
    --cc=shh.xie@gmail.com \
    --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).