All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Christoph Niedermaier <cniedermaier@dh-electronics.com>,
	Fabio Estevam <festevam@denx.de>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Peng Fan <peng.fan@nxp.com>, Rob Herring <robh+dt@kernel.org>,
	NXP Linux Team <linux-imx@nxp.com>,
	kernel@dh-electronics.com
Subject: Re: [PATCH v2 3/4] dt-bindings: arm: Split i.MX8M Plus DHCOM based boards
Date: Sun, 1 Jan 2023 11:28:41 +0800	[thread overview]
Message-ID: <20230101032840.GR6112@T480> (raw)
In-Reply-To: <20221216210244.591865-3-marex@denx.de>

On Fri, Dec 16, 2022 at 10:02:43PM +0100, Marek Vasut wrote:
> The i.MX8M Plus DHCOM based boards have compatible string in the form:
> "vendor,custom-board", "dh,som", "fsl,soc"
> or
> "dh,carrier-board", "dh,som", "fsl,soc"
> Split the binding entry so this triplet can be matched on.
> 
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Marek Vasut <marex@denx.de>

It doesn't apply to my imx/bindings branch.  Could you rebase and resend
the series?

Shawn

  reply	other threads:[~2023-01-01  3:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 21:02 [PATCH v2 1/4] dt-bindings: arm: Move MX8Menlo board to i.MX8M Mini Toradex Verdin SoM entry Marek Vasut
2022-12-16 21:02 ` [PATCH v2 2/4] dt-bindings: arm: Split i.MX8M Mini NITROGEN SoM based boards Marek Vasut
2022-12-16 21:02 ` [PATCH v2 3/4] dt-bindings: arm: Split i.MX8M Plus DHCOM " Marek Vasut
2023-01-01  3:28   ` Shawn Guo [this message]
2023-01-05 14:02     ` Marek Vasut
2022-12-16 21:02 ` [PATCH v2 4/4] dt-bindings: arm: Move i.MX8MM Cloos PHG Board to TQM entry Marek Vasut
2022-12-16 21:27   ` Fabio Estevam
2022-12-16 21:25 ` [PATCH v2 1/4] dt-bindings: arm: Move MX8Menlo board to i.MX8M Mini Toradex Verdin SoM entry Francesco Dolcini
2022-12-16 21:35   ` Marek Vasut
2022-12-20 18:21 ` Rob Herring
2022-12-21  8:36 ` Krzysztof Kozlowski

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=20230101032840.GR6112@T480 \
    --to=shawnguo@kernel.org \
    --cc=cniedermaier@dh-electronics.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@denx.de \
    --cc=kernel@dh-electronics.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-imx@nxp.com \
    --cc=marex@denx.de \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@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 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.