linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leo Li <leoyang.li@nxp.com>
To: Rob Herring <robh@kernel.org>
Cc: Shawn Guo <shawnguo@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH 02/11] dt-bindings: fsl,layerscape-dcfg: add missing compatible for lx2160a
Date: Mon, 29 Nov 2021 23:28:28 +0000	[thread overview]
Message-ID: <AS8PR04MB894647B096661C2030EB84F98F669@AS8PR04MB8946.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <YaU91SxgAFXtDMyW@robh.at.kernel.org>



> -----Original Message-----
> From: Rob Herring <robh@kernel.org>
> Sent: Monday, November 29, 2021 2:54 PM
> To: Leo Li <leoyang.li@nxp.com>
> Cc: Shawn Guo <shawnguo@kernel.org>; Michael Turquette
> <mturquette@baylibre.com>; Stephen Boyd <sboyd@kernel.org>;
> devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org
> Subject: Re: [PATCH 02/11] dt-bindings: fsl,layerscape-dcfg: add missing
> compatible for lx2160a
> 
> On Wed, Nov 10, 2021 at 04:21:51PM -0600, Li Yang wrote:
> > The compatbile string is already in use, fix the chip list in binding to
> 
> same typo.
> 
> > include it.
> >
> > Signed-off-by: Li Yang <leoyang.li@nxp.com>
> > ---
> >  .../devicetree/bindings/arm/freescale/fsl,layerscape-dcfg.txt   | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Acked-by: Rob Herring <robh@kernel.org>

Thanks.  Both typo fixed and applied to fsl-soc tree.

Regards,
Leo

  reply	other threads:[~2021-11-29 23:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 22:21 [PATCH 00/11] lx216x DTS updates Li Yang
2021-11-10 22:21 ` [PATCH 01/11] dt-bindings: qoriq-clock: add missing compatible for lx2160a Li Yang
2021-11-29 20:50   ` Rob Herring
2021-11-10 22:21 ` [PATCH 02/11] dt-bindings: fsl,layerscape-dcfg: " Li Yang
2021-11-29 20:53   ` Rob Herring
2021-11-29 23:28     ` Leo Li [this message]
2021-11-10 22:21 ` [PATCH 03/11] arm64: dts: lx2160a: fix scl-gpios property name Li Yang
2021-11-10 22:21 ` [PATCH 04/11] arm64: dts: lx2160a-rdb: Add Inphi PHY node Li Yang
2021-11-10 22:21 ` [PATCH 05/11] arm64: dts: lx2160a: add optee-tz node Li Yang
2021-11-10 22:21 ` [PATCH 06/11] arm64: dts: lx2160a-qds: enable sata nodes Li Yang
2021-11-10 23:48   ` Leo Li
2021-11-10 22:21 ` [PATCH 07/11] arm64: dts: lx2160aqds: Add mdio mux nodes Li Yang
2021-11-10 22:21 ` [PATCH 08/11] arm64: dts: lx2160a: update PCIe nodes to match rev2 silicon Li Yang
2021-11-10 22:21 ` [PATCH 09/11] arm64: dts: lx2160a: add pcie EP mode nodes Li Yang
2021-11-10 22:21 ` [PATCH 10/11] arm64: dts: lx2160a: enable usb3-lpm-capable for usb3 nodes Li Yang
2021-11-10 22:22 ` [PATCH 11/11] arm64: dts: lx2162aqds: support SD UHS-I and eMMC HS400 modes Li Yang

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=AS8PR04MB894647B096661C2030EB84F98F669@AS8PR04MB8946.eurprd04.prod.outlook.com \
    --to=leoyang.li@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).