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/3][pull request] Intel Wired LAN Driver Updates 2023-03-07 (ice)
Date: Thu, 09 Mar 2023 11:00:18 +0000 [thread overview]
Message-ID: <167835961869.26114.12268235898612114211.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230307220714.3997294-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 Tue, 7 Mar 2023 14:07:11 -0800 you wrote:
> This series contains updates to ice driver only.
>
> Dave removes masking from pfcena field as it was incorrectly preventing
> valid traffic classes from being enabled.
>
> Michal resolves various smatch issues such as not propagating error
> codes and returning 0 explicitly.
>
> [...]
Here is the summary with links:
- [net,1/3] ice: Fix DSCP PFC TLV creation
https://git.kernel.org/netdev/net/c/fef3f92e8a42
- [net,2/3] ice: don't ignore return codes in VSI related code
https://git.kernel.org/netdev/net/c/c4a9c8e78aad
- [net,3/3] ethernet: ice: avoid gcc-9 integer overflow warning
https://git.kernel.org/netdev/net/c/8f5c5a790e30
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-03-09 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 22:07 [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2023-03-07 (ice) Tony Nguyen
2023-03-07 22:07 ` [PATCH net 1/3] ice: Fix DSCP PFC TLV creation Tony Nguyen
2023-03-07 22:07 ` [PATCH net 2/3] ice: don't ignore return codes in VSI related code Tony Nguyen
2023-03-07 22:07 ` [PATCH net 3/3] ethernet: ice: avoid gcc-9 integer overflow warning Tony Nguyen
2023-03-09 11:00 ` 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=167835961869.26114.12268235898612114211.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.