devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo2@yeah.net>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Stefan Agner <stefan@agner.ch>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/4] arm: fsl: drop usage of Toradex SOMs compatible alone
Date: Tue, 11 Mar 2025 11:17:18 +0800	[thread overview]
Message-ID: <Z8+rPvG177Csh2m1@dragon> (raw)
In-Reply-To: <20250228151352.91768-1-francesco@dolcini.it>

On Fri, Feb 28, 2025 at 04:13:48PM +0100, Francesco Dolcini wrote:
> From: Francesco Dolcini <francesco.dolcini@toradex.com>
> 
> The Toradex SOMs cannot be used alone without a carrier board, so drop
> the usage of its compatible alone.
> 
> Francesco Dolcini (4):
>   dt-bindings: arm: fsl: drop usage of Toradex SOMs compatible alone
>   ARM: dts: imx6qdl-apalis/colibri: Remove compatible from SoM dtsi
>   arm64: dts: imx8qm-apalis: Remove compatible from SoM dtsi
>   ARM: dts: vf610-colibri: Remove compatible from SoM dtsi

Applied all, thanks!


      parent reply	other threads:[~2025-03-11  3:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 15:13 [PATCH v2 0/4] arm: fsl: drop usage of Toradex SOMs compatible alone Francesco Dolcini
2025-02-28 15:13 ` [PATCH v2 1/4] dt-bindings: " Francesco Dolcini
2025-02-28 15:13 ` [PATCH v2 2/4] ARM: dts: imx6qdl-apalis/colibri: Remove compatible from SoM dtsi Francesco Dolcini
2025-02-28 15:13 ` [PATCH v2 3/4] arm64: dts: imx8qm-apalis: " Francesco Dolcini
2025-02-28 15:13 ` [PATCH v2 4/4] ARM: dts: vf610-colibri: " Francesco Dolcini
2025-03-11  3:17 ` Shawn Guo [this message]

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=Z8+rPvG177Csh2m1@dragon \
    --to=shawnguo2@yeah.net \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=francesco@dolcini.it \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    /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).