public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Dong Yibo <dong100@mucse.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, corbet@lwn.net,
	andrew+netdev@lunn.ch, danishanwar@ti.com,
	vadim.fedorenko@linux.dev, geert+renesas@glider.be,
	mpe@ellerman.id.au, lorenzo@kernel.org, lukas.bulwahn@redhat.com,
	netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v17 0/5] Add driver for 1Gbe network chips from MUCSE
Date: Wed, 05 Nov 2025 02:20:21 +0000	[thread overview]
Message-ID: <176230922174.3062547.13202635035807581684.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251101013849.120565-1-dong100@mucse.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sat,  1 Nov 2025 09:38:44 +0800 you wrote:
> Hi maintainers,
> 
> This patch series adds support for MUCSE RNPGBE 1Gbps PCIe Ethernet controllers
> (N500/N210 series), including build infrastructure, hardware initialization,
> mailbox (MBX) communication with firmware, and basic netdev registration
> (Can show mac witch is got from firmware, and tx/rx will be added later).
> 
> [...]

Here is the summary with links:
  - [net-next,v17,1/5] net: rnpgbe: Add build support for rnpgbe
    https://git.kernel.org/netdev/net-next/c/ee61c10cd482
  - [net-next,v17,2/5] net: rnpgbe: Add n500/n210 chip support with BAR2 mapping
    https://git.kernel.org/netdev/net-next/c/1b7f85f733fd
  - [net-next,v17,3/5] net: rnpgbe: Add basic mbx ops support
    https://git.kernel.org/netdev/net-next/c/4543534c3ef5
  - [net-next,v17,4/5] net: rnpgbe: Add basic mbx_fw support
    https://git.kernel.org/netdev/net-next/c/c6d3f0198eaa
  - [net-next,v17,5/5] net: rnpgbe: Add register_netdev
    https://git.kernel.org/netdev/net-next/c/2ee95ec17e97

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-11-05  2:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-01  1:38 [PATCH net-next v17 0/5] Add driver for 1Gbe network chips from MUCSE Dong Yibo
2025-11-01  1:38 ` [PATCH net-next v17 1/5] net: rnpgbe: Add build support for rnpgbe Dong Yibo
2025-11-01  1:38 ` [PATCH net-next v17 2/5] net: rnpgbe: Add n500/n210 chip support with BAR2 mapping Dong Yibo
2025-11-01  1:38 ` [PATCH net-next v17 3/5] net: rnpgbe: Add basic mbx ops support Dong Yibo
2025-11-01  1:38 ` [PATCH net-next v17 4/5] net: rnpgbe: Add basic mbx_fw support Dong Yibo
2025-11-01  1:38 ` [PATCH net-next v17 5/5] net: rnpgbe: Add register_netdev Dong Yibo
2025-11-05  2:20 ` 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=176230922174.3062547.13202635035807581684.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=danishanwar@ti.com \
    --cc=davem@davemloft.net \
    --cc=dong100@mucse.com \
    --cc=edumazet@google.com \
    --cc=geert+renesas@glider.be \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=lukas.bulwahn@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vadim.fedorenko@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