From: patchwork-bot+netdevbpf@kernel.org
To: Minda Chen <minda.chen@starfivetech.com>
Cc: alexandre.torgue@foss.st.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com,
emil.renner.berthing@canonical.com, robh+dt@kernel.org,
krzk+dt@kernel.org, conor@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
devicetree@vger.kernel.org
Subject: Re: [net-next v5 0/4] Add StarFive jhb100 soc SGMII GMAC support
Date: Tue, 02 Jun 2026 03:10:19 +0000 [thread overview]
Message-ID: <178036981914.224606.5617424802966318344.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260527084108.121416-1-minda.chen@starfivetech.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 27 May 2026 16:41:04 +0800 you wrote:
> jhb100 is a Starfive new RISC-V SoC for datacenter BMC (BaseBoard
> Managent Controller). Similar with Aspeed 27x0.
>
> The jhb100 minimal system upstream is in progress:
> https://patchwork.kernel.org/project/linux-riscv/cover/20260508053632.818548-1-changhuang.liang@starfivetech.com/
>
> jhb100 GMAC still using designware GMAC core like JH7100 and JH7110,
> and contains 2 SGMII interfaces, 1 RGMII/RMII interface, 1 RMII
> interface. In JH7100/JH7110 dwmac-starfive.c have supported RGMII/RMII
> interface. So require to add SGMII support to dwmac-starfive.c for JHB100.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/4] dt-bindings: net: starfive,jh7110-dwmac: Remove jh8100
https://git.kernel.org/netdev/net-next/c/106ce4a01c17
- [net-next,v5,2/4] dt-bindings: net: starfive,jh7110-dwmac: Add jhb100 support
https://git.kernel.org/netdev/net-next/c/64772e4d06a5
- [net-next,v5,3/4] net: stmmac: starfive: Add jhb100 SGMII interface
https://git.kernel.org/netdev/net-next/c/98182c748125
- [net-next,v5,4/4] net: stmmac: starfive: Add STMMAC_FLAG_SPH_DISABLE flag
https://git.kernel.org/netdev/net-next/c/7e9ea8de277a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-02 3:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 8:41 [net-next v5 0/4] Add StarFive jhb100 soc SGMII GMAC support Minda Chen
2026-05-27 8:41 ` [net-next v5 1/4] dt-bindings: net: starfive,jh7110-dwmac: Remove jh8100 Minda Chen
2026-05-27 8:41 ` [net-next v5 2/4] dt-bindings: net: starfive,jh7110-dwmac: Add jhb100 support Minda Chen
2026-05-30 0:49 ` sashiko-bot
2026-05-27 8:41 ` [net-next v5 3/4] net: stmmac: starfive: Add jhb100 SGMII interface Minda Chen
2026-05-27 8:41 ` [net-next v5 4/4] net: stmmac: starfive: Add STMMAC_FLAG_SPH_DISABLE flag Minda Chen
2026-06-02 3:10 ` patchwork-bot+netdevbpf [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=178036981914.224606.5617424802966318344.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=emil.renner.berthing@canonical.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=minda.chen@starfivetech.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.