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 0/2][pull request] Intel Wired LAN Driver Updates 2022-11-30 (e1000e, igb)
Date: Fri, 02 Dec 2022 04:20:15 +0000 [thread overview]
Message-ID: <166995481530.23610.6478921023189893172.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221130194228.3257787-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net.git (master)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Wed, 30 Nov 2022 11:42:26 -0800 you wrote:
> This series contains updates to e1000e and igb drivers.
>
> Akihiko Odaki fixes calculation for checking whether space for next
> frame exists for e1000e and properly sets MSI-X vector to fix failing
> ethtool interrupt test for igb.
>
> The following are changes since commit 01f856ae6d0ca5ad0505b79bf2d22d7ca439b2a1:
> Merge tag 'net-6.1-rc8-2' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue 1GbE
>
> [...]
Here is the summary with links:
- [net,1/2] e1000e: Fix TX dispatch condition
https://git.kernel.org/netdev/net/c/eed913f6919e
- [net,2/2] igb: Allocate MSI-X vector when testing
https://git.kernel.org/netdev/net/c/28e96556baca
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:[~2022-12-02 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 19:42 [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2022-11-30 (e1000e, igb) Tony Nguyen
2022-11-30 19:42 ` [PATCH net 1/2] e1000e: Fix TX dispatch condition Tony Nguyen
2022-11-30 19:42 ` [PATCH net 2/2] igb: Allocate MSI-X vector when testing Tony Nguyen
2022-12-02 4: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=166995481530.23610.6478921023189893172.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.