From: Nishanth Menon <nm@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <kristo@kernel.org>
Subject: Re: [PATCH 0/2] arm64: dts: ti: k3-j721e: dtbs_check warnings fixups
Date: Tue, 6 Jun 2023 11:14:04 -0500 [thread overview]
Message-ID: <20230606161404.e35m5snkytpfxvxt@emoticon> (raw)
In-Reply-To: <20230424154841.353631-1-nm@ti.com>
On 10:48-20230424, Nishanth Menon wrote:
> Hi,
>
> Minor series of two patches to fixup the pending dtbs_check warnings in
> j721e.
>
> Nishanth Menon (2):
> arm64: dts: ti: k3-j721e-mcu-wakeup: Switch to
> "ti,j721e-system-controller" compatible
> arm64: dts: ti: k3-j721e-mcu-wakeup: Fix fss node name
>
> arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --
> 2.40.0
>
As discussed in https://lore.kernel.org/all/20230605205220.rjmcsi5tjn4auqa7@arose/
Lets drop this series, once the dependent patches are merged, we can
switch to bus in the next kernel rev.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-06-06 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 15:48 [PATCH 0/2] arm64: dts: ti: k3-j721e: dtbs_check warnings fixups Nishanth Menon
2023-04-24 15:48 ` [PATCH 1/2] arm64: dts: ti: k3-j721e-mcu-wakeup: Switch to "ti,j721e-system-controller" compatible Nishanth Menon
2023-06-05 15:13 ` Raghavendra, Vignesh
2023-06-05 20:52 ` Nishanth Menon
2023-04-24 15:48 ` [PATCH 2/2] arm64: dts: ti: k3-j721e-mcu-wakeup: Fix fss node name Nishanth Menon
2023-06-06 16:14 ` Nishanth Menon [this message]
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=20230606161404.e35m5snkytpfxvxt@emoticon \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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