mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vikas Gupta <vikas.gupta@broadcom.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
	vsrama-krishna.nemani@broadcom.com
Subject: Re: [net-next, v3 00/10] Introducing Broadcom BNGE Ethernet Driver
Date: Tue, 08 Jul 2025 02:10:44 +0000	[thread overview]
Message-ID: <175194064425.3543842.3986154137074104629.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250701143511.280702-1-vikas.gupta@broadcom.com>

Hello:

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

On Tue,  1 Jul 2025 14:34:58 +0000 you wrote:
> Hi,
> 
> This patch series introduces the Ethernet driver for Broadcom’s
> BCM5770X chip family, which supports 50/100/200/400/800 Gbps
> link speeds. The driver is built as the bng_en.ko kernel module.
> 
> To keep the series within a reviewable size (~5K lines of code), this initial
> submission focuses on the core infrastructure and initialization, including:
> 1) PCIe support (device IDs, probe/remove)
> 2) Devlink support
> 3) Firmware communication mechanism
> 4) Creation of network device
> 5) PF Resource management (rings, IRQs, etc. for netdev & aux dev)
> 
> [...]

Here is the summary with links:
  - [net-next,v3,01/10] bng_en: Add PCI interface
    https://git.kernel.org/netdev/net-next/c/74715c4ab0fa
  - [net-next,v3,02/10] bng_en: Add devlink interface
    https://git.kernel.org/netdev/net-next/c/9099bfa1158a
  - [net-next,v3,03/10] bng_en: Add firmware communication mechanism
    https://git.kernel.org/netdev/net-next/c/7037d1d89796
  - [net-next,v3,04/10] bng_en: Add initial interaction with firmware
    https://git.kernel.org/netdev/net-next/c/fb7d8b61c1f7
  - [net-next,v3,05/10] bng_en: Add ring memory allocation support
    https://git.kernel.org/netdev/net-next/c/27544c0ecb4c
  - [net-next,v3,06/10] bng_en: Add backing store support
    https://git.kernel.org/netdev/net-next/c/29c5b358f385
  - [net-next,v3,07/10] bng_en: Add resource management support
    https://git.kernel.org/netdev/net-next/c/627c67f038d2
  - [net-next,v3,08/10] bng_en: Add irq allocation support
    https://git.kernel.org/netdev/net-next/c/18a975389fcc
  - [net-next,v3,09/10] bng_en: Initialize default configuration
    https://git.kernel.org/netdev/net-next/c/3fa9e977a0cd
  - [net-next,v3,10/10] bng_en: Add a network device
    https://git.kernel.org/netdev/net-next/c/13a68c1ed754

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-07-08  2:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 14:34 Vikas Gupta
2025-07-01 14:34 ` [net-next, v3 01/10] bng_en: Add PCI interface Vikas Gupta
2025-07-01 14:35 ` [net-next, v3 02/10] bng_en: Add devlink interface Vikas Gupta
2025-07-01 14:35 ` [net-next, v3 03/10] bng_en: Add firmware communication mechanism Vikas Gupta
2025-07-01 14:35 ` [net-next, v3 04/10] bng_en: Add initial interaction with firmware Vikas Gupta
2025-07-01 14:35 ` [net-next, v3 05/10] bng_en: Add ring memory allocation support Vikas Gupta
2025-07-01 14:35 ` [net-next, v3 06/10] bng_en: Add backing store support Vikas Gupta
2025-07-01 14:35 ` [net-next, v3 07/10] bng_en: Add resource management support Vikas Gupta
2025-07-01 14:35 ` [net-next, v3 08/10] bng_en: Add irq allocation support Vikas Gupta
2025-07-01 14:35 ` [net-next, v3 09/10] bng_en: Initialize default configuration Vikas Gupta
2025-07-01 14:35 ` [net-next, v3 10/10] bng_en: Add a network device Vikas Gupta
2025-07-08  2: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=175194064425.3543842.3986154137074104629.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pavan.chebbi@broadcom.com \
    --cc=vikas.gupta@broadcom.com \
    --cc=vsrama-krishna.nemani@broadcom.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

all inboxes | Powered by JetHome®