From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net v3 0/3][pull request] Intel Wired LAN Driver Updates 2023-06-12 (igc, igb)
Date: Thu, 15 Jun 2023 05:50:19 +0000 [thread overview]
Message-ID: <168680821983.19671.18140959822703552463.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230612205208.115292-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net.git (main)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Mon, 12 Jun 2023 13:52:05 -0700 you wrote:
> This series contains updates to igc and igb drivers.
>
> Husaini clears Tx rings when interface is brought down for igc.
>
> Vinicius disables PTM and PCI busmaster when removing igc driver.
>
> Alex adds error check and path for NVM read error on igb.
>
> [...]
Here is the summary with links:
- [net,v3,1/3] igc: Clean the TX buffer and TX descriptor ring
https://git.kernel.org/netdev/net/c/e43516f5978d
- [net,v3,2/3] igc: Fix possible system crash when loading module
https://git.kernel.org/netdev/net/c/c080fe262f9e
- [net,v3,3/3] igb: fix nvm.ops.read() error handling
https://git.kernel.org/netdev/net/c/48a821fd5883
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:[~2023-06-15 5:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 20:52 [PATCH net v3 0/3][pull request] Intel Wired LAN Driver Updates 2023-06-12 (igc, igb) Tony Nguyen
2023-06-12 20:52 ` [PATCH net v3 1/3] igc: Clean the TX buffer and TX descriptor ring Tony Nguyen
2023-06-12 20:52 ` [PATCH net v3 2/3] igc: Fix possible system crash when loading module Tony Nguyen
2023-06-12 20:52 ` [PATCH net v3 3/3] igb: fix nvm.ops.read() error handling Tony Nguyen
2023-06-13 7:54 ` Fijalkowski, Maciej
2023-06-15 5:50 ` 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=168680821983.19671.18140959822703552463.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.