linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Inochi Amaoto <inochiama@gmail.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Chen Wang <unicorn_wang@outlook.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	Richard Cochran <richardcochran@gmail.com>,
	Alexander Sverdlin <alexander.sverdlin@gmail.com>,
	Yixun Lan <dlan@gentoo.org>,
	Thomas Bonnefille <thomas.bonnefille@bootlin.com>,
	Ze Huang <huangze@whut.edu.cn>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
	sophgo@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org,
	Longbin Li <looong.bin@gmail.com>
Subject: Re: [PATCH net-next RFC v4 0/4] riscv: dts: sophgo: Add ethernet support for cv18xx
Date: Tue, 1 Jul 2025 08:26:31 +0200	[thread overview]
Message-ID: <a5107266-853e-4658-ba90-d6a08882d2a8@kernel.org> (raw)
In-Reply-To: <vxnvovuetfd6rzgaenwplpkhxm62fhw6t3vi4wkyigul7p4bkx@pwlprna4pyul>

On 01/07/2025 03:23, Inochi Amaoto wrote:
> On Tue, Jul 01, 2025 at 09:17:25AM +0800, Inochi Amaoto wrote:
>> Add device binding and dts for CV18XX series SoC, this dts change series
>> required the reset patch [1] for the dts, which is already taken.
>>
>> [1] https://lore.kernel.org/all/20250617070144.1149926-1-inochiama@gmail.com
>>
>> The patch is marked as RFC as it require reset dts.
>>
>> Change from RFC v3:
>> - https://lore.kernel.org/all/20250626080056.325496-1-inochiama@gmail.com
>> 1. patch 3: change internal phy id from 0 to 1
>>
>> Change from RFC v2:
>> - https://lore.kernel.org/all/20250623003049.574821-1-inochiama@gmail.com
>> 1. patch 1: fix wrong binding title
>> 2. patch 3: fix unmatched mdio bus number
>> 3. patch 4: remove setting phy-mode and phy-handle in board dts and move
>> 	    them into patch 3.
>>
>> Change from RFC v1:
>> - https://lore.kernel.org/all/20250611080709.1182183-1-inochiama@gmail.com
>> 1. patch 3: switch to mdio-mux-mmioreg
>> 2. patch 4: add configuration for Huashan Pi
>>
>> Inochi Amaoto (4):
>>   dt-bindings: net: Add support for Sophgo CV1800 dwmac
>>   riscv: dts: sophgo: Add ethernet device for cv18xx
>>   riscv: dts: sophgo: Add mdio multiplexer device for cv18xx
>>   riscv: dts: sophgo: Enable ethernet device for Huashan Pi
>>
>>  .../bindings/net/sophgo,cv1800b-dwmac.yaml    | 113 ++++++++++++++++++
>>  arch/riscv/boot/dts/sophgo/cv180x.dtsi        |  73 +++++++++++
>>  .../boot/dts/sophgo/cv1812h-huashan-pi.dts    |   8 ++
>>  3 files changed, 194 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/net/sophgo,cv1800b-dwmac.yaml
>>
>> --
>> 2.50.0
>>
> 
> As this is mark as RFC due to the reset dependency, now it is OK
> to merge it as the reset patch is taken and this patch is a minor
> change . I hopeif anyone can take the binding patch so I can take
> the devicetree patches.

I don't understand why you target net-next with your DTS patches. The
subject prefix is here not correct and probably this should be split.
Anyway, bindings have issues, so no, it cannot be merged.

Best regards,
Krzysztof

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-07-01  7:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01  1:17 [PATCH net-next RFC v4 0/4] riscv: dts: sophgo: Add ethernet support for cv18xx Inochi Amaoto
2025-07-01  1:17 ` [PATCH net-next RFC v4 1/4] dt-bindings: net: Add support for Sophgo CV1800 dwmac Inochi Amaoto
2025-07-01  6:25   ` Krzysztof Kozlowski
2025-07-01  1:17 ` [PATCH net-next RFC v4 2/4] riscv: dts: sophgo: Add ethernet device for cv18xx Inochi Amaoto
2025-07-01  1:17 ` [PATCH net-next RFC v4 3/4] riscv: dts: sophgo: Add mdio multiplexer " Inochi Amaoto
2025-07-01  1:17 ` [PATCH net-next RFC v4 4/4] riscv: dts: sophgo: Enable ethernet device for Huashan Pi Inochi Amaoto
2025-07-01  1:23 ` [PATCH net-next RFC v4 0/4] riscv: dts: sophgo: Add ethernet support for cv18xx Inochi Amaoto
2025-07-01  6:26   ` Krzysztof Kozlowski [this message]
2025-07-01 10:04     ` Inochi Amaoto

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=a5107266-853e-4658-ba90-d6a08882d2a8@kernel.org \
    --to=krzk@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=alexander.sverdlin@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@gentoo.org \
    --cc=edumazet@google.com \
    --cc=huangze@whut.edu.cn \
    --cc=inochiama@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=looong.bin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=richardcochran@gmail.com \
    --cc=robh@kernel.org \
    --cc=sophgo@lists.linux.dev \
    --cc=thomas.bonnefille@bootlin.com \
    --cc=unicorn_wang@outlook.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;
as well as URLs for NNTP newsgroup(s).