All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: kuba@kernel.org, netdev@vger.kernel.org, davem@davemloft.net,
	aleksander.lobakin@intel.com, michal.kubiak@intel.com,
	wojciech.drewek@intel.com, horms@kernel.org,
	krishneil.k.singh@intel.com, himasekharx.reddy.pucha@intel.com
Subject: Re: [PATCH net 0/2] Intel Wired LAN Driver Updates 2024-05-23 (ice, idpf)
Date: Tue, 28 May 2024 00:20:30 +0000	[thread overview]
Message-ID: <171685563078.6024.17644411462995653095.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240523-net-2024-05-23-intel-net-fixes-v1-0-17a923e0bb5f@intel.com>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 23 May 2024 10:45:28 -0700 you wrote:
> This series contains two fixes which finished up testing.
> 
> First, Alexander fixes an issue in idpf caused by enabling NAPI and
> interrupts prior to actually allocating the Rx buffers.
> 
> Second, Jacob fixes the ice driver VSI VLAN counting logic to ensure that
> addition and deletion of VLANs properly manages the total VSI count.
> 
> [...]

Here is the summary with links:
  - [net,1/2] idpf: don't enable NAPI and interrupts prior to allocating Rx buffers
    https://git.kernel.org/netdev/net/c/d514c8b54209
  - [net,2/2] ice: fix accounting if a VLAN already exists
    https://git.kernel.org/netdev/net/c/82617b9a0464

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-05-28  0:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 17:45 [PATCH net 0/2] Intel Wired LAN Driver Updates 2024-05-23 (ice, idpf) Jacob Keller
2024-05-23 17:45 ` [PATCH net 1/2] idpf: don't enable NAPI and interrupts prior to allocating Rx buffers Jacob Keller
2024-05-23 17:45 ` [PATCH net 2/2] ice: fix accounting if a VLAN already exists Jacob Keller
2024-05-23 19:46   ` Simon Horman
2024-05-28  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=171685563078.6024.17644411462995653095.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aleksander.lobakin@intel.com \
    --cc=davem@davemloft.net \
    --cc=himasekharx.reddy.pucha@intel.com \
    --cc=horms@kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=krishneil.k.singh@intel.com \
    --cc=kuba@kernel.org \
    --cc=michal.kubiak@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=wojciech.drewek@intel.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.