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 2024-04-03 (ice, idpf)
Date: Thu, 04 Apr 2024 16:40:30 +0000 [thread overview]
Message-ID: <171224883056.6883.7867699699844132113.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240403201929.1945116-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 Wed, 3 Apr 2024 13:19:25 -0700 you wrote:
> This series contains updates to ice and idpf drivers.
>
> Dan Carpenter initializes some pointer declarations to NULL as needed for
> resource cleanup on ice driver.
>
> Petr Oros corrects assignment of VLAN operators to fix Rx VLAN filtering
> in legacy mode for ice.
>
> [...]
Here is the summary with links:
- [net,1/3] ice: Fix freeing uninitialized pointers
https://git.kernel.org/netdev/net/c/90ca6956d383
- [net,2/3] ice: fix enabling RX VLAN filtering
https://git.kernel.org/netdev/net/c/8edfc7a40e33
- [net,3/3] idpf: fix kernel panic on unknown packet types
https://git.kernel.org/netdev/net/c/dd19e827d63a
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:[~2024-04-04 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 20:19 [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2024-04-03 (ice, idpf) Tony Nguyen
2024-04-03 20:19 ` [PATCH net 1/3] ice: Fix freeing uninitialized pointers Tony Nguyen
2024-04-03 20:19 ` [PATCH net 2/3] ice: fix enabling RX VLAN filtering Tony Nguyen
2024-04-03 20:19 ` [PATCH net 3/3] idpf: fix kernel panic on unknown packet types Tony Nguyen
2024-04-04 16:40 ` 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=171224883056.6883.7867699699844132113.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 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).