Thread (25 messages) flat view 25 messages, 4 authors, 5d ago

Re: [PATCH PRELIMINARY 0/5] arm64: dts: qcom: shikra: add Ethernet support

From: Mohd Ayaan Anwar <mohd.anwar@oss.qualcomm.com>
Date: 2026-09-08 10:02:57
Also in: linux-arm-msm, linux-devicetree, lkml

On Tue, Sep 08, 2026 at 10:42:40AM +0200, Krzysztof Kozlowski wrote:
On 08/09/2026 09:39, Mohd Ayaan Anwar wrote:
quoted
On Tue, Sep 08, 2026 at 12:53:46PM +0530, Mohd Ayaan Anwar wrote:
quoted
On Tue, Sep 08, 2026 at 09:14:45AM +0200, Krzysztof Kozlowski wrote:
quoted
On 08/09/2026 09:04, Mohd Ayaan Anwar wrote:
quoted
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.
...would it be preferable to instead have the split like this?

  - This series + dt-bindings (on top of linux-next)
  - Only driver changes from [1] (for net-next)
No, because it would be against explicit documented rules in the kernel
and against clear guidelines and recent discussions within Qualcomm. I
wonder why did we have these long discussions about Shikra if only a few
people were listening and the rest will be repeating the same broken
process as before?
Understood, thanks. I'll keep the current split (bindings + driver to
net-next, DTS separate for the SoC tree).

	Ayaan
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help