From: Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com>
To: Shawn Guo <shengchao.guo@oss.qualcomm.com>
Cc: 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, sibi.sankar@oss.qualcomm.com,
rajendra.nayak@oss.qualcomm.com
Subject: Re: [PATCH] arm64: dts: qcom: Move board nodes to common DTSI
Date: Mon, 18 May 2026 16:13:44 +0530 [thread overview]
Message-ID: <734cf62b-e896-4089-8c8e-5b773ae7df5e@oss.qualcomm.com> (raw)
In-Reply-To: <ac3i5MIlEQ6y9SNp@QCOM-aGQu4IUr3Y>
On 4/2/2026 9:00 AM, Shawn Guo wrote:
> On Thu, Mar 26, 2026 at 07:21:01AM -0700, Gopikrishna Garmidi wrote:
>> The display, peripherals (touchpad/touchscreen/keypad), usb and their
>> dependent device nodes are common to both Glymur and Mahua CRDs,
>> so move them from glymur-crd.dts to glymur-crd.dtsi to enable code
>> reuse.
>>
>> Signed-off-by: Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com>
>
> You may want to have glymur-crd on the subject prefix to tell the scope
> of the change.
Sure, will fix it in the next version.
Thanks,
Gopikrishna
prev parent reply other threads:[~2026-05-18 10:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 14:21 [PATCH] arm64: dts: qcom: Move board nodes to common DTSI Gopikrishna Garmidi
2026-03-26 14:25 ` Krzysztof Kozlowski
2026-03-26 16:55 ` Sibi Sankar
2026-03-27 6:45 ` Krzysztof Kozlowski
2026-03-27 12:46 ` Gopikrishna Garmidi
2026-03-29 10:57 ` Dmitry Baryshkov
2026-05-15 9:14 ` Pankaj Patil
2026-05-24 18:23 ` Krzysztof Kozlowski
2026-05-25 13:57 ` Gopikrishna Garmidi
2026-04-02 3:30 ` Shawn Guo
2026-05-18 10:43 ` Gopikrishna Garmidi [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=734cf62b-e896-4089-8c8e-5b773ae7df5e@oss.qualcomm.com \
--to=gopikrishna.garmidi@oss.qualcomm.com \
--cc=andersson@kernel.org \
--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=rajendra.nayak@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=shengchao.guo@oss.qualcomm.com \
--cc=sibi.sankar@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