From: Sasha Levin <sashal@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Saravana Kannan <saravanak@google.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [GIT PULL] Devicetree updates for v6.13
Date: Sun, 24 Nov 2024 11:59:39 -0500 [thread overview]
Message-ID: <Z0NbeyTwxo-M4Lgi@sashalap> (raw)
In-Reply-To: <c25e6a80-f6dc-4ef9-a90d-0fa09cbbc217@linaro.org>
On Sun, Nov 24, 2024 at 05:47:33PM +0100, Krzysztof Kozlowski wrote:
>On 24/11/2024 17:29, Sasha Levin wrote:
>> Hi Rob,
>>
>> On Mon, Nov 18, 2024 at 03:07:30PM -0600, Rob Herring wrote:
>>> of: WARN on deprecated #address-cells/#size-cells handling
>>
>> With the commit above, I've started seeing boot warnings on a few
>
>And same boards do not report problems on the next?
Looks like they do. I haven't checked it previously, but I see that we
have similar warnings on a few boards that KernelCI is testing -next on.
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-11-24 16:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 21:07 [GIT PULL] Devicetree updates for v6.13 Rob Herring
2024-11-20 22:56 ` pr-tracker-bot
2024-11-24 16:29 ` Sasha Levin
2024-11-24 16:47 ` Krzysztof Kozlowski
2024-11-24 16:59 ` Sasha Levin [this message]
2024-11-25 9:48 ` AngeloGioacchino Del Regno
2024-11-25 10:34 ` Chen-Yu Tsai
2024-11-25 11:00 ` Krzysztof Kozlowski
2024-11-25 11:33 ` Krzysztof Kozlowski
2024-11-25 12:11 ` AngeloGioacchino Del Regno
2024-11-25 13:24 ` Sasha Levin
2024-11-25 15:15 ` Rob Herring
2024-12-09 9:28 ` Chen-Yu Tsai
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=Z0NbeyTwxo-M4Lgi@sashalap \
--to=sashal@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=torvalds@linux-foundation.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).