From: Mohd Ayaan Anwar <mohd.anwar@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
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>,
Komal Bajaj <komal.bajaj@oss.qualcomm.com>,
Anurag Pateriya <apateriy@qti.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Richard Cochran <richardcochran@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH PRELIMINARY 0/5] arm64: dts: qcom: shikra: add Ethernet support
Date: Tue, 8 Sep 2026 12:53:37 +0530 [thread overview]
Message-ID: <ap+3+Xhq6ygnPzQ7@oss.qualcomm.com> (raw)
In-Reply-To: <c23369fc-84ff-4881-8327-c18fc3692306@kernel.org>
On Tue, Sep 08, 2026 at 09:14:45AM +0200, Krzysztof Kozlowski wrote:
> On 08/09/2026 09:04, Mohd Ayaan Anwar wrote:
> > On Tue, Sep 08, 2026 at 08:56:39AM +0200, Krzysztof Kozlowski wrote:
> >> On 08/09/2026 08:23, Mohd Ayaan Anwar wrote:
> >>> Hi,
> >>>
> >>> This preliminary series adds the DTS changes required to enable
> >>> Ethernet on the Qualcomm Shikra CQM, CQS, and IQS EVKs.
> >>
> >> What is "PRELIMINARY" patch in upstream? Where is this process
> >> documented or expressed?
> >>
> >
> > My apologies. The code is ready, and I was hoping that sharing the DTS
> > changes would make reviewing the driver and dt-bindings a bit easier.
> > The original RFC had them together, and I split it out for net-next
> > and linux-next.
>
> Yeah, but why calling it completely different than every other patchset?
> Why coming with different style? Why this cannot be RFC?
Agreed. In hindsight, this should probably have been an RFC v2. I saw
some recent series using a PRELIMINARY tag, but I see that its
ultimately just an RFC.
>
> >
> > The only reason I added a PRELIMINARY tag was because these DTS changes
> > should go in after the driver changes and dt-bindings.
> >
>
> DTS cannot go after the driver changes. If that is your requirement,
> then original work is broken and needs to be fixed.
>
I should have worded it better. I am only worried about the dt-bindings
going in before this DTS. The driver changes just add support for
whatever we are desribing in this series, they can go in after
dt-bindings and DTS without any issues.
Ayaan
next prev parent reply other threads:[~2026-09-08 7:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 6:23 Mohd Ayaan Anwar
2026-09-08 6:23 ` [PATCH PRELIMINARY 1/5] arm64: dts: qcom: shikra-iqs-som: fix GPIO138 reservation Mohd Ayaan Anwar
2026-09-08 12:11 ` Andrew Lunn
2026-09-08 13:43 ` Mohd Ayaan Anwar
2026-09-08 13:57 ` Andrew Lunn
2026-09-09 11:20 ` Konrad Dybcio
2026-09-09 11:19 ` Konrad Dybcio
2026-09-09 11:24 ` Krzysztof Kozlowski
2026-09-09 11:30 ` Krzysztof Kozlowski
2026-09-09 11:33 ` Krzysztof Kozlowski
2026-09-09 11:39 ` Mohd Ayaan Anwar
2026-09-09 11:34 ` Mohd Ayaan Anwar
2026-09-08 6:23 ` [PATCH PRELIMINARY 2/5] arm64: dts: qcom: shikra: add ethernet nodes Mohd Ayaan Anwar
2026-09-08 6:23 ` [PATCH PRELIMINARY 3/5] arm64: dts: qcom: shikra-cqm-evk: enable the first Ethernet port Mohd Ayaan Anwar
2026-09-08 6:23 ` [PATCH PRELIMINARY 4/5] arm64: dts: qcom: shikra-cqs-evk: " Mohd Ayaan Anwar
2026-09-08 6:23 ` [PATCH PRELIMINARY 5/5] arm64: dts: qcom: shikra-iqs-evk: enable both Ethernet ports Mohd Ayaan Anwar
2026-09-08 6:56 ` [PATCH PRELIMINARY 0/5] arm64: dts: qcom: shikra: add Ethernet support Krzysztof Kozlowski
2026-09-08 7:04 ` Mohd Ayaan Anwar
2026-09-08 7:14 ` Krzysztof Kozlowski
2026-09-08 7:23 ` Mohd Ayaan Anwar [this message]
2026-09-08 7:39 ` Mohd Ayaan Anwar
2026-09-08 8:42 ` Krzysztof Kozlowski
2026-09-08 10:02 ` Mohd Ayaan Anwar
2026-09-08 8:40 ` Krzysztof Kozlowski
2026-09-08 9:31 ` Mohd Ayaan Anwar
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=ap+3+Xhq6ygnPzQ7@oss.qualcomm.com \
--to=mohd.anwar@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=apateriy@qti.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=komal.bajaj@oss.qualcomm.com \
--cc=konrad.dybcio@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=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--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
all inboxes | Powered by JetHome®