From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Pierre Yves MORDRET <frq08952@lmecxl1060.lme.st.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: <linux-stm32@st-md-mailman.stormreply.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Pierre-Yves MORDRET <pierre-yves.mordret@foss.st.com>,
Philippe Cornu <philippe.cornu@foss.st.com>,
Marcin Sloniewski <marcin.sloniewski@gmail.com>,
Reinhold Mueller <reinhold.mueller@emtrion.com>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH v2 0/3] YAML validation fixes
Date: Mon, 3 Apr 2023 10:11:46 +0200 [thread overview]
Message-ID: <c2a80960-f92f-0919-bf82-d5cec74fda09@foss.st.com> (raw)
In-Reply-To: <20230119144030.1805-1-pierre-yves.mordret@foss.st.com>
Hi
On 1/19/23 15:40, Pierre Yves MORDRET wrote:
> Attention: Sender not authenticated
> --------------------------------------------------
>
> Patches to get rid from DT check errors for STM32MPU Boards but also for Argon and Odyssey.
>
> ---
> Version history:
> v1:
> * Initial
> v2:
> * Update send addresses
>
> Pierre-Yves MORDRET (3):
> ARM: dts: stm32: YAML validation fails for STM32MPU Boards
> ARM: dts: stm32: YAML validation fails for Odyssey Boards
> ARM: dts: stm32: YAML validation fails for Argon Boards
>
> arch/arm/boot/dts/stm32mp157c-ed1.dts | 9 ---------
> arch/arm/boot/dts/stm32mp157c-emstamp-argon.dtsi | 9 ---------
> arch/arm/boot/dts/stm32mp157c-odyssey-som.dtsi | 10 ----------
> arch/arm/boot/dts/stm32mp15xx-dkx.dtsi | 9 ---------
> 4 files changed, 37 deletions(-)
>
> --
> 2.17.1
>
Series applied on stm32-next.
Regards
Alex
parent reply other threads:[~2023-04-03 8:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230119144030.1805-1-pierre-yves.mordret@foss.st.com>]
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=c2a80960-f92f-0919-bf82-d5cec74fda09@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=a.fatoum@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=frq08952@lmecxl1060.lme.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marcin.sloniewski@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=philippe.cornu@foss.st.com \
--cc=pierre-yves.mordret@foss.st.com \
--cc=reinhold.mueller@emtrion.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 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).