From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
sassmann@redhat.com
Subject: Re: [PATCH net-next 00/10][pull request] 100GbE Intel Wired LAN Driver Updates 2021-03-23
Date: Wed, 24 Mar 2021 00:20:09 +0000 [thread overview]
Message-ID: <161654520992.13502.16093262378436187844.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210323190149.3160859-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 23 Mar 2021 12:01:39 -0700 you wrote:
> This series contains updates to ice, fm10k, i40e, iavf, ixgbe, ixgbevf,
> igb, e1000e, and e1000 drivers.
>
> Tony fixes prototype warnings for mismatched header for ice driver.
>
> Sasha fixes prototype warnings for mismatched header for igc and e1000e
> driver.
>
> [...]
Here is the summary with links:
- [net-next,01/10] ice: Fix prototype warnings
https://git.kernel.org/netdev/net-next/c/ef860480ea18
- [net-next,02/10] igc: Fix prototype warning
https://git.kernel.org/netdev/net-next/c/c4cdb4efa20c
- [net-next,03/10] e1000e: Fix prototype warning
https://git.kernel.org/netdev/net-next/c/39da2cac42d4
- [net-next,04/10] intel: clean up mismatched header comments
https://git.kernel.org/netdev/net-next/c/262de08f64e3
- [net-next,05/10] ice: Fix fall-through warnings for Clang
https://git.kernel.org/netdev/net-next/c/9ded647a5141
- [net-next,06/10] fm10k: Fix fall-through warnings for Clang
https://git.kernel.org/netdev/net-next/c/f83a0d0adac6
- [net-next,07/10] ixgbe: Fix fall-through warnings for Clang
https://git.kernel.org/netdev/net-next/c/27e40255e5ac
- [net-next,08/10] igb: Fix fall-through warnings for Clang
https://git.kernel.org/netdev/net-next/c/52c406989a51
- [net-next,09/10] ixgbevf: Fix fall-through warnings for Clang
https://git.kernel.org/netdev/net-next/c/d8f0c306985e
- [net-next,10/10] e1000: Fix fall-through warnings for Clang
https://git.kernel.org/netdev/net-next/c/67831a08a778
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:[~2021-03-24 0:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 19:01 [PATCH net-next 00/10][pull request] 100GbE Intel Wired LAN Driver Updates 2021-03-23 Tony Nguyen
2021-03-23 19:01 ` [PATCH net-next 01/10] ice: Fix prototype warnings Tony Nguyen
2021-03-23 19:01 ` [PATCH net-next 02/10] igc: Fix prototype warning Tony Nguyen
2021-03-23 19:01 ` [PATCH net-next 03/10] e1000e: " Tony Nguyen
2021-03-23 19:01 ` [PATCH net-next 04/10] intel: clean up mismatched header comments Tony Nguyen
2021-03-23 19:01 ` [PATCH net-next 05/10] ice: Fix fall-through warnings for Clang Tony Nguyen
2021-03-23 19:01 ` [PATCH net-next 06/10] fm10k: " Tony Nguyen
2021-03-23 19:01 ` [PATCH net-next 07/10] ixgbe: " Tony Nguyen
2021-03-23 19:01 ` [PATCH net-next 08/10] igb: " Tony Nguyen
2021-03-23 19:01 ` [PATCH net-next 09/10] ixgbevf: " Tony Nguyen
2021-03-23 19:01 ` [PATCH net-next 10/10] e1000: " Tony Nguyen
2021-03-24 0: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=161654520992.13502.16093262378436187844.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sassmann@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).