From: Bjorn Andersson <andersson@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Abel Vesa <abel.vesa@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: eliza: Add CPU and LLCC BWMONs
Date: Wed, 15 Jul 2026 12:16:36 -0500 [thread overview]
Message-ID: <ale-YM2Aa7nrpGcY@baldur> (raw)
In-Reply-To: <CAL_JsqK8vEN48DrS=aAyu7QMrMZVTWGCSADPPcgwAd77GzCPGQ@mail.gmail.com>
On Tue, Jul 14, 2026 at 05:18:28PM -0500, Rob Herring wrote:
> On Thu, Jul 9, 2026 at 2:32 PM Bjorn Andersson <andersson@kernel.org> wrote:
> >
> >
> > On Wed, 08 Jul 2026 15:29:23 +0300, Abel Vesa wrote:
> > > Describe the CPU and LLCC bandwidth monitor nodes for Eliza, together
> > > with the corresponding OPP tables.
> > >
> > >
> >
> > Applied, thanks!
> >
> > [1/1] arm64: dts: qcom: eliza: Add CPU and LLCC BWMONs
> > commit: 4e967cad02bce8983c4e826cd13ef0e730692832
>
> Either wait for the binding to be applied or apply the binding with
> this if it is a binding only change with no driver changes so that we
> can have fewer intermittent warnings.
My bad, I always dtbs_check against the linux-next processed-schema
before pushing out. I'm trying to figure out why that didn't catch this
and the missing Shikra bindings :(
> It didn't help that it was not a series.
>
That would have been helpful...
> I'm applying the binding.
>
Thank you!
Regards,
Bjorn
> Rob
prev parent reply other threads:[~2026-07-15 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 12:29 [PATCH] arm64: dts: qcom: eliza: Add CPU and LLCC BWMONs Abel Vesa
2026-07-08 13:22 ` Dmitry Baryshkov
2026-07-08 13:41 ` Konrad Dybcio
2026-07-09 19:32 ` Bjorn Andersson
2026-07-14 22:18 ` Rob Herring
2026-07-15 17:16 ` Bjorn Andersson [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=ale-YM2Aa7nrpGcY@baldur \
--to=andersson@kernel.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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