From: Shawn Guo <shawnguo@kernel.org>
To: Marcel Ziswiler <marcel@ziswiler.com>
Cc: devicetree@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, Stefan Agner <stefan@agner.ch>,
Philippe Schenker <philippe.schenker@toradex.com>,
Rob Herring <robh+dt@kernel.org>,
linux-imx@nxp.com,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/5] arm: dts: vf-colibri: fix typo in top-level module compatible
Date: Mon, 4 Nov 2019 09:16:58 +0800 [thread overview]
Message-ID: <20191104011657.GE24620@dragon> (raw)
In-Reply-To: <20191026090403.3057-1-marcel@ziswiler.com>
On Sat, Oct 26, 2019 at 11:03:59AM +0200, Marcel Ziswiler wrote:
> From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>
> Fix typo in top-level module compatible.
>
> Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>
> ---
>
> Changes in v2: New patch.
>
> arch/arm/boot/dts/vf500-colibri.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/vf500-colibri.dtsi b/arch/arm/boot/dts/vf500-colibri.dtsi
> index 237b0246fa84..92255f8893ce 100644
> --- a/arch/arm/boot/dts/vf500-colibri.dtsi
> +++ b/arch/arm/boot/dts/vf500-colibri.dtsi
> @@ -44,7 +44,7 @@
>
> / {
> model = "Toradex Colibri VF50 COM";
> - compatible = "toradex,vf610-colibri_vf50", "fsl,vf500";
> + compatible = "toradex,vf500-colibri_vf50", "fsl,vf500";
Do we need to update bindings doc for this?
Also as a practise, we use 'ARM: ...' for arch/arm/ patches going through
IMX tree.
Shawn
>
> memory@80000000 {
> device_type = "memory";
> --
> 2.21.0
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-04 1:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 9:03 [PATCH v2 1/5] arm: dts: vf-colibri: fix typo in top-level module compatible Marcel Ziswiler
2019-10-26 9:04 ` [PATCH v2 2/5] dt-bindings: arm: fsl: add nxp based toradex apalis/colibri binding docu Marcel Ziswiler
2019-10-30 14:03 ` Rob Herring
2019-11-04 1:25 ` Shawn Guo
2019-10-26 9:04 ` [PATCH v2 3/5] dt-bindings: input: tochscreen: ad7879: generic node names in example Marcel Ziswiler
2019-10-30 14:04 ` Rob Herring
2019-10-30 14:04 ` Rob Herring
2019-10-30 23:12 ` Dmitry Torokhov
2019-11-06 8:58 ` Marcel Ziswiler
2019-11-12 0:05 ` dmitry.torokhov
2019-10-26 9:04 ` [PATCH v2 4/5] arm64: dts: freescale: add initial support for colibri imx8x Marcel Ziswiler
2019-10-26 9:04 ` [PATCH v2 5/5] dt-bindings: arm: fsl: add nxp based toradex colibri-imx8x binding docu Marcel Ziswiler
2019-10-30 14:05 ` Rob Herring
2019-11-04 1:26 ` Shawn Guo
2019-11-04 1:16 ` Shawn Guo [this message]
2019-11-04 1:20 ` [PATCH v2 1/5] arm: dts: vf-colibri: fix typo in top-level module compatible Shawn Guo
2019-11-04 1:29 ` Shawn Guo
2019-11-04 6:51 ` Marcel Ziswiler
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=20191104011657.GE24620@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=marcel@ziswiler.com \
--cc=mark.rutland@arm.com \
--cc=philippe.schenker@toradex.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--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).