From: Shawn Guo <shawnguo@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Sean Anderson <sean.anderson@seco.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Li Yang <leoyang.li@nxp.com>, Rob Herring <robh+dt@kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Walle <michael@walle.cc>
Subject: Re: [PATCH v4 1/4] arm64: dts: ls1028a: Update SFP binding to include clock
Date: Tue, 5 Jul 2022 09:09:42 +0800 [thread overview]
Message-ID: <20220705010942.GS819983@dragon> (raw)
In-Reply-To: <9448e378-35cd-a39c-869c-845605cbee84@linaro.org>
On Mon, Jul 04, 2022 at 10:27:40AM +0200, Krzysztof Kozlowski wrote:
> On 01/07/2022 00:32, Sean Anderson wrote:
> > The clocks property is now mandatory. Add it.
> >
> > Fixes: eba5bea8f37f ("arm64: dts: ls1028a: add efuse node")
> > Signed-off-by: Sean Anderson <sean.anderson@seco.com>
> > Reviewed-by: Michael Walle <michael@walle.cc>
>
> The subjects of all these 4 patches are confusing - you did not
> update/add any binding here. These are not bindings.
Right, I replaced 'binding' with 'node' during applying.
Shawn
next prev parent reply other threads:[~2022-07-05 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 22:32 [PATCH v4 0/4] nvmem: sfp: binding updates Sean Anderson
2022-06-30 22:32 ` [PATCH v4 1/4] arm64: dts: ls1028a: Update SFP binding to include clock Sean Anderson
2022-07-04 8:27 ` Krzysztof Kozlowski
2022-07-05 1:09 ` Shawn Guo [this message]
2022-06-30 22:32 ` [PATCH v4 2/4] arm64: dts: layerscape: Add SFP binding for TA 2.1 devices Sean Anderson
2022-06-30 22:32 ` [PATCH v4 3/4] ARM: " Sean Anderson
2022-06-30 22:32 ` [PATCH v4 4/4] arm64: dts: Add SFP binding for TA 3.0 devices Sean Anderson
2022-07-05 1:08 ` [PATCH v4 0/4] nvmem: sfp: binding updates Shawn Guo
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=20220705010942.GS819983@dragon \
--to=shawnguo@kernel.org \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=robh+dt@kernel.org \
--cc=sean.anderson@seco.com \
--cc=srinivas.kandagatla@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).