From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Alexander Koskovich <AKoskovich@pm.me>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sm8250: Add label for reserved-memory node
Date: Mon, 9 Mar 2026 12:03:34 +0100 [thread overview]
Message-ID: <a6d052fd-c704-48ca-b267-b594a5c4c886@oss.qualcomm.com> (raw)
In-Reply-To: <cifklloa2hp6yt7o6kphjydq2mkpqs23avyqa22tsrf5xjsw6v@cgkvft5nossn>
On 3/8/26 3:59 PM, Dmitry Baryshkov wrote:
> On Sun, Mar 08, 2026 at 11:52:07AM +0000, Alexander Koskovich wrote:
>> On Sunday, March 8th, 2026 at 4:46 AM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>>> There is no user for this, so change is pointless. labels do not exist
>>> in DTBs, so drop the entire patch or provide here - in the same commit -
>>> proper user.
>>
>> Want to submit the ROG 3 in a follow up change but was trying to get
>> all dependencies for it merged beforehand.
>>
>> Should I just upload the devicetree and link to relevant patches?
>
> It might be eaiser to submit DT with all DT dependencies in a single
> series. Then the reviewers can see the reasons for your changes
> and provide a more complete review.
Such oneliners, I wouldn't even bother putting in a separate commit
Konrad
prev parent reply other threads:[~2026-03-09 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 5:05 [PATCH] arm64: dts: qcom: sm8250: Add label for reserved-memory node Alexander Koskovich
2026-03-08 8:46 ` Krzysztof Kozlowski
2026-03-08 11:52 ` Alexander Koskovich
2026-03-08 14:59 ` Dmitry Baryshkov
2026-03-09 11:03 ` Konrad Dybcio [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=a6d052fd-c704-48ca-b267-b594a5c4c886@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=AKoskovich@pm.me \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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