From: Yann GAUTIER <yann.gautier@foss.st.com>
To: Marek Vasut <marex@denx.de>,
<linux-arm-kernel@lists.infradead.org>,
Linus Walleij <linus.walleij@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: <devicetree@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Alexandre Torgue <alexandre.torgue@st.com>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [Linux-stm32] [PATCH V2] ARM: dts: stm32: Rename mmc controller nodes to mmc@
Date: Mon, 25 Jan 2021 13:58:22 +0100 [thread overview]
Message-ID: <eb8c62eb-87c1-0011-49ae-260239daf79e@foss.st.com> (raw)
In-Reply-To: <20210124170337.32917-1-marex@denx.de>
On 1/24/21 6:03 PM, Marek Vasut wrote:
> Per mmc-controller.yaml, the node pattern is"^mmc(@.*)?$" ,
> so adjust the node.
>
> Signed-off-by: Marek Vasut<marex@denx.de>
> Cc: Alexandre Torgue<alexandre.torgue@st.com>
> Cc: Ludovic Barre<ludovic.barre@st.com>
> Cc: Ulf Hansson<ulf.hansson@linaro.org>
> Cc:linux-stm32@st-md-mailman.stormreply.com
> Cc:devicetree@vger.kernel.org
Hi Marek,
Acked-by: Yann Gautier <yann.gautier@foss.st.com>
Do you know if similar patches are planned for other platform using this
IP (Qualcom, ST-Ericsson, Arm vexpress...)?
I found issues with them when running this command:
make -k dtbs_check
DT_SCHEMA_FILES=Documentation/devicetree/bindings/mmc/arm,pl18x.yaml
Maybe Linus already sent the info?
Adding those other platforms maintainers.
Regards,
Yann
next prev parent reply other threads:[~2021-01-26 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 17:03 [PATCH V2] ARM: dts: stm32: Rename mmc controller nodes to mmc@ Marek Vasut
2021-01-25 12:58 ` Yann GAUTIER [this message]
2021-01-25 13:02 ` [Linux-stm32] " Marek Vasut
2021-01-25 13:33 ` Linus Walleij
2021-01-25 14:29 ` Alexandre TORGUE
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=eb8c62eb-87c1-0011-49ae-260239daf79e@foss.st.com \
--to=yann.gautier@foss.st.com \
--cc=agross@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=marex@denx.de \
--cc=sudeep.holla@arm.com \
--cc=ulf.hansson@linaro.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).