From: Andrew Lunn <andrew@lunn.ch>
To: 李志 <lizhi2@eswincomputing.com>
Cc: sashiko-reviews@lists.linux.dev, conor+dt@kernel.org,
robh@kernel.org, devicetree@vger.kernel.org,
Min Lin <linmin@eswincomputing.com>
Subject: Re: Re: [PATCH net-next v9 6/6] riscv: dts: eswin: eic7700-hifive-premier-p550: enable Ethernet controller
Date: Thu, 2 Jul 2026 15:22:34 +0200 [thread overview]
Message-ID: <58532b95-bb74-4d87-acae-e67b41dd7d57@lunn.ch> (raw)
In-Reply-To: <5de09a24.a11e.19f2207d7d2.Coremail.lizhi2@eswincomputing.com>
> Hi Andrew,
>
> One question before I prepare the next revision.
>
> As discussed previously, the DTS patch was included only to provide the overall
> Ethernet design context during the review of the binding and driver patches:
>
> https://lore.kernel.org/lkml/64bf6b40-b947-4ffa-8d48-4d6341931327@lunn.ch/
>
> For the next revision, would it be acceptable to drop the DTS patch from this
> series and post only the binding and driver patches? The complete DTS
> enablement is planned to be submitted later as a separate series after the
> binding and driver have been merged.
What normally happens is that I give an Acked-by: or a Reviewed-by:
for the DT patch, and you submit it for merging via the DT Maintainer.
Everything then meets up in linux-next.
Why do you need to do this later? Why not now?
Andrew
next prev parent reply other threads:[~2026-07-02 13:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 6:31 [PATCH net-next v9 0/6] net: stmmac: eic7700: add eth1 variant support and update delay bindings lizhi2
2026-06-30 6:32 ` [PATCH net-next v9 1/6] dt-bindings: ethernet: eswin: relax internal delay model to range-based constraints lizhi2
2026-06-30 6:32 ` [PATCH net-next v9 2/6] dt-bindings: ethernet: eswin: add EIC7700 eth1 RX clock inversion variant lizhi2
2026-06-30 7:10 ` Maxime Chevallier
2026-06-30 17:14 ` Conor Dooley
2026-06-30 6:32 ` [PATCH net-next v9 3/6] net: stmmac: eic7700: make RGMII delay properties optional lizhi2
2026-06-30 6:33 ` [PATCH net-next v9 4/6] net: stmmac: eic7700: add support for eth1 clock inversion variant lizhi2
2026-06-30 6:34 ` [PATCH net-next v9 5/6] dt-bindings: mfd: syscon: add ESWIN EIC7700 compatible lizhi2
2026-06-30 6:34 ` [PATCH net-next v9 6/6] riscv: dts: eswin: eic7700-hifive-premier-p550: enable Ethernet controller lizhi2
2026-07-01 6:35 ` sashiko-bot
2026-07-02 8:52 ` 李志
2026-07-02 13:22 ` Andrew Lunn [this message]
2026-07-03 1:50 ` 李志
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=58532b95-bb74-4d87-acae-e67b41dd7d57@lunn.ch \
--to=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linmin@eswincomputing.com \
--cc=lizhi2@eswincomputing.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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