Netdev List
 help / color / mirror / Atom feed
From: 李志 <lizhi2@eswincomputing.com>
To: "Paolo Abeni" <pabeni@redhat.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
	sashiko-reviews@lists.linux.dev, conor+dt@kernel.org,
	robh@kernel.org, devicetree@vger.kernel.org,
	"Min Lin" <linmin@eswincomputing.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Re: [PATCH net-next v9 6/6] riscv: dts: eswin: eic7700-hifive-premier-p550: enable Ethernet controller
Date: Tue, 7 Jul 2026 09:39:41 +0800 (GMT+08:00)	[thread overview]
Message-ID: <5d02cc6b.a380.19f3a3b21b7.Coremail.lizhi2@eswincomputing.com> (raw)
In-Reply-To: <41d0e6d6-f1fc-425e-a122-b0433a925a3d@redhat.com>




> -----Original Messages-----
> From: "Paolo Abeni" <pabeni@redhat.com>
> Send time:Monday, 06/07/2026 21:35:40
> To: 李志 <lizhi2@eswincomputing.com>, "Andrew Lunn" <andrew@lunn.ch>
> Cc: sashiko-reviews@lists.linux.dev, conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org, "Min Lin" <linmin@eswincomputing.com>, "netdev@vger.kernel.org" <netdev@vger.kernel.org>
> Subject: Re: [PATCH net-next v9 6/6] riscv: dts: eswin: eic7700-hifive-premier-p550: enable Ethernet controller
> 
> On 7/3/26 3:50 AM, 李志 wrote:
> >> -----Original Messages-----
> >> From: "Andrew Lunn" <andrew@lunn.ch>
> >> Send time:Thursday, 02/07/2026 21:22:34
> >> 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
> >>
> >>> 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?
> >>
> > 
> > There is an another seperate DT patch series
> > [https://lore.kernel.org/all/20260615122016.1110206-1-pinkesh.vaghela@einfochips.com/]
> > which is under review.
> > It also introduces DT nodes for reset, clock, pinctrl, HSP power domain.
> > 
> > Therefore, our planned steps are as follows:
> > 1. In the next net-next v10​ patch series, drop the DTS patches, and submit only
> >    the bindings and driver.
> > 2. Wait for Pinkesh’s DT patch series​ to be merged.
> > 3. Once the HSPCRG patch series​
> >    [https://lore.kernel.org/all/20260605060730.1605-1-dongxuyang@eswincomputing.com/]
> >    is merged, submit a new DT patch series​ to extend ESWIN EIC7700 SoC support​
> >    for all HSP modules—including USB, eMMC, SD, and Ethernet, since they are all
> >    under the HSP bus node eventhough ethernet doese not depend on HSPCRG patch.
> 
> In v10 please include some actual description of the series, beyond the
> changelog.
> 

OK, thanks.

For v10, we'll drop the DTS patches (patches 5 and 6 in v9) from this
series and update the cover letter to include a proper description of
the series.

      reply	other threads:[~2026-07-07  1:39 UTC|newest]

Thread overview: 14+ 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-06 13:09   ` Paolo Abeni
2026-07-06 13:21     ` Conor Dooley
2026-07-06 13:34       ` Paolo Abeni
     [not found]   ` <20260701063512.9ED051F000E9@smtp.kernel.org>
     [not found]     ` <5de09a24.a11e.19f2207d7d2.Coremail.lizhi2@eswincomputing.com>
     [not found]       ` <58532b95-bb74-4d87-acae-e67b41dd7d57@lunn.ch>
     [not found]         ` <f21ffca.a15e.19f25abaea6.Coremail.lizhi2@eswincomputing.com>
2026-07-06 13:35           ` Paolo Abeni
2026-07-07  1:39             ` 李志 [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=5d02cc6b.a380.19f3a3b21b7.Coremail.lizhi2@eswincomputing.com \
    --to=lizhi2@eswincomputing.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linmin@eswincomputing.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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