From: Rob Herring <robh@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev
Subject: Re: [PATCH v4 0/8] arm64: dts: convert fsl,esdhc.txt to yaml and fix layerscape dts warning
Date: Tue, 11 Jun 2024 14:16:31 -0600 [thread overview]
Message-ID: <20240611201631.GA3003237-robh@kernel.org> (raw)
In-Reply-To: <20240611-ls_waring_esdhc-v4-0-d0d8a5b3f3cb@nxp.com>
On Tue, Jun 11, 2024 at 12:01:45PM -0400, Frank Li wrote:
> Start from v4 because fsl.esdhc.txt to yaml already sent out as v3.
>
> Change from v3 to v4
> - Add dts warning fixes
> - Add mmc-spi-slot's voltage range fix, (not sure why it apply to
> layserscape's dts file.
> - clock-frequency is not required property
> - add dma-conherence: true in binding doc
>
> Now only "bit-endian" proptery warning left.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> Frank Li (8):
> dt-bindings: mmc: Convert fsl-esdhc.txt to yaml
> dt-bindings: mmc: mmc-spi-slot: Change voltage-ranges to uint32-matrix
> arm64: dts: ls1012a: Chang node name from 'esdhc' to 'mmc'
> arm64: dts: ls1043a: Chang node name from 'esdhc' to 'mmc'
> arm64: dts: ls1046a: Chang node name from 'esdhc' to 'mmc'
> arm64: dts: ls1088a: Chang node name from 'esdhc' to 'mmc'
> arm64: dts: ls208ax: Chang node name from 'esdhc' to 'mmc'
> arm64: dts: lx2160a: Chang node name from 'esdhc' to 'mmc'
It is all the same change to the same maintainer, so these can be just
one patch. Then you just have 1 typo to fix.
Rob
next prev parent reply other threads:[~2024-06-11 20:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 16:01 [PATCH v4 0/8] arm64: dts: convert fsl,esdhc.txt to yaml and fix layerscape dts warning Frank Li
2024-06-11 16:01 ` [PATCH v4 1/8] dt-bindings: mmc: Convert fsl-esdhc.txt to yaml Frank Li
2024-06-12 6:30 ` Krzysztof Kozlowski
2024-06-11 16:01 ` [PATCH v4 2/8] dt-bindings: mmc: mmc-spi-slot: Change voltage-ranges to uint32-matrix Frank Li
2024-06-11 20:23 ` Rob Herring
2024-06-12 14:36 ` Frank Li
2024-06-13 6:35 ` Krzysztof Kozlowski
2024-06-11 16:01 ` [PATCH v4 3/8] arm64: dts: ls1012a: Chang node name from 'esdhc' to 'mmc' Frank Li
2024-06-11 16:01 ` [PATCH v4 4/8] arm64: dts: ls1043a: " Frank Li
2024-06-11 16:01 ` [PATCH v4 5/8] arm64: dts: ls1046a: " Frank Li
2024-06-11 16:01 ` [PATCH v4 6/8] arm64: dts: ls1088a: " Frank Li
2024-06-11 16:01 ` [PATCH v4 7/8] arm64: dts: ls208ax: " Frank Li
2024-06-11 16:01 ` [PATCH v4 8/8] arm64: dts: lx2160a: " Frank Li
2024-06-11 18:48 ` [PATCH v4 0/8] arm64: dts: convert fsl,esdhc.txt to yaml and fix layerscape dts warning Dragan Simic
2024-06-11 20:16 ` Rob Herring [this message]
2024-06-12 6:31 ` 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=20240611201631.GA3003237-robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawnguo@kernel.org \
--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).