netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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-next 0/6][pull request] Intel Wired LAN Driver Updates 2022-11-04 (ixgbe, ixgbevf, igb)
Date: Tue, 08 Nov 2022 04:00:19 +0000	[thread overview]
Message-ID: <166788001902.28960.4724643167535301112.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221104205414.2354973-1-anthony.l.nguyen@intel.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Tony Nguyen <anthony.l.nguyen@intel.com>:

On Fri,  4 Nov 2022 13:54:08 -0700 you wrote:
> This series contains updates to ixgbe, ixgbevf, and igb drivers.
> 
> Daniel Willenson adjusts descriptor buffer limits to be based on what
> hardware supports instead of using a generic, least common value for
> ixgbe.
> 
> Ani removes local variable for ixgbe, instead returning conditional result
> directly.
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] ixgbe: change MAX_RXD/MAX_TXD based on adapter type
    https://git.kernel.org/netdev/net-next/c/864f88884c42
  - [net-next,2/6] ixgbe: Remove local variable
    https://git.kernel.org/netdev/net-next/c/6a6f9e3e03ae
  - [net-next,3/6] ixgbe: Remove unneeded semicolon
    https://git.kernel.org/netdev/net-next/c/f49fafa504d5
  - [net-next,4/6] ixgbevf: Add error messages on vlan error
    https://git.kernel.org/netdev/net-next/c/eac0b6804b74
  - [net-next,5/6] igb: Do not free q_vector unless new one was allocated
    https://git.kernel.org/netdev/net-next/c/0668716506ca
  - [net-next,6/6] igb: Proactively round up to kmalloc bucket size
    https://git.kernel.org/netdev/net-next/c/e9d696cb44e3

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



      parent reply	other threads:[~2022-11-08  4:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 20:54 [PATCH net-next 0/6][pull request] Intel Wired LAN Driver Updates 2022-11-04 (ixgbe, ixgbevf, igb) Tony Nguyen
2022-11-04 20:54 ` [PATCH net-next 1/6] ixgbe: change MAX_RXD/MAX_TXD based on adapter type Tony Nguyen
2022-11-04 20:54 ` [PATCH net-next 2/6] ixgbe: Remove local variable Tony Nguyen
2022-11-04 20:54 ` [PATCH net-next 3/6] ixgbe: Remove unneeded semicolon Tony Nguyen
2022-11-04 20:54 ` [PATCH net-next 4/6] ixgbevf: Add error messages on vlan error Tony Nguyen
2022-11-04 20:54 ` [PATCH net-next 5/6] igb: Do not free q_vector unless new one was allocated Tony Nguyen
2022-11-07  7:03   ` Leon Romanovsky
2022-11-07 13:55     ` Ruhl, Michael J
2022-11-07 17:45       ` Leon Romanovsky
2022-11-07 18:35         ` Jacob Keller
2022-11-08  3:55           ` Jakub Kicinski
2022-11-04 20:54 ` [PATCH net-next 6/6] igb: Proactively round up to kmalloc bucket size Tony Nguyen
2022-11-07  7:05 ` [PATCH net-next 0/6][pull request] Intel Wired LAN Driver Updates 2022-11-04 (ixgbe, ixgbevf, igb) Leon Romanovsky
2022-11-08  4: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=166788001902.28960.4724643167535301112.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).