From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Scott Branden <sbranden@broadcom.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Ray Jui <rjui@broadcom.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH 2/2] arm64: dts: broadcom: align SPI NOR node name with dtschema
Date: Wed, 20 Apr 2022 10:52:45 +0200 [thread overview]
Message-ID: <2079f567-ff8f-5790-cba7-837c311e5fce@linaro.org> (raw)
In-Reply-To: <20220407185710.2576287-1-f.fainelli@gmail.com>
On 07/04/2022 20:57, Florian Fainelli wrote:
> On Thu, 7 Apr 2022 16:32:11 +0200, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
>> The node names should be generic and SPI NOR dtschema expects "flash".
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>
> Applied to https://github.com/Broadcom/stblinux/commits/devicetree-arm64/next, thanks!
Thanks Florian. It seems that patch is still not in linux-next. Is your
tree included in the linux-next?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-20 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 14:32 [PATCH 1/2] ARM: dts: broadcom: align SPI NOR node name with dtschema Krzysztof Kozlowski
2022-04-07 14:32 ` [PATCH 2/2] arm64: " Krzysztof Kozlowski
2022-04-07 18:57 ` Florian Fainelli
2022-04-20 8:52 ` Krzysztof Kozlowski [this message]
2022-06-25 3:43 ` Florian Fainelli
2022-04-07 18:55 ` [PATCH 1/2] ARM: " Florian Fainelli
2022-04-07 18:58 ` Florian Fainelli
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=2079f567-ff8f-5790-cba7-837c311e5fce@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
/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).