From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>, arm@kernel.org, soc@kernel.org
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
Sumit Garg <sumit.garg@oss.qualcomm.com>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Daniel J Blueman <daniel@quora.org>,
Ravi Hothi <ravi.hothi@oss.qualcomm.com>
Subject: Re: [GIT PULL] Qualcomm Arm64 DeviceTree fixes for v7.0
Date: Fri, 27 Mar 2026 09:01:54 +0100 [thread overview]
Message-ID: <31bfba49-2cc8-439c-b08c-f75b853fe993@kernel.org> (raw)
In-Reply-To: <20260326133845.66761-1-andersson@kernel.org>
On 26/03/2026 14:38, Bjorn Andersson wrote:
>
> ----------------------------------------------------------------
> Daniel J Blueman (1):
> arm64: dts: qcom: hamoa/x1: fix idle exit latency
>
> Loic Poulain (2):
> arm64: dts: qcom: monaco: Fix UART10 pinconf
> arm64: dts: qcom: monaco: Reserve full Gunyah metadata region
>
> Ravi Hothi (1):
> arm64: dts: qcom: qcm6490-idp: Fix WCD9370 reset GPIO polarity
>
> Sumit Garg (3):
> dt-bindings: display: msm: qcm2290-mdss: Fix iommus property
This introduces a known warning, which I already reported and pinged you
TWICE on IRC, including yesterday. I did not indicate that my fix is for
current cycle, because I did not know that troubling commit is part of
the fixes branch.
No, I am not taking a known warning without fix, especially that the fix
is right there.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-03-27 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 13:38 [GIT PULL] Qualcomm Arm64 DeviceTree fixes for v7.0 Bjorn Andersson
2026-03-27 8:01 ` Krzysztof Kozlowski [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=31bfba49-2cc8-439c-b08c-f75b853fe993@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=daniel@quora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=ravi.hothi@oss.qualcomm.com \
--cc=soc@kernel.org \
--cc=sumit.garg@oss.qualcomm.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