All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, pabeni@redhat.com,
	edumazet@google.com
Subject: Re: [PATCH net-next 0/6] net: switch drivers to netif_napi_add_weight()
Date: Sun, 08 May 2022 10:50:14 +0000	[thread overview]
Message-ID: <165200701497.399.16357279983705677828.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220506170751.822862-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri,  6 May 2022 10:07:45 -0700 you wrote:
> The minority of drivers pass a custom weight to netif_napi_add().
> Switch those away to the new netif_napi_add_weight(). All drivers
> (which can go thru net-next) calling netif_napi_add() will now
> be calling it with NAPI_POLL_WEIGHT or 64.
> 
> Jakub Kicinski (6):
>   um: vector: switch to netif_napi_add_weight()
>   caif_virtio: switch to netif_napi_add_weight()
>   eth: switch to netif_napi_add_weight()
>   r8152: switch to netif_napi_add_weight()
>   net: virtio: switch to netif_napi_add_weight()
>   net: wan: switch to netif_napi_add_weight()
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] um: vector: switch to netif_napi_add_weight()
    https://git.kernel.org/netdev/net-next/c/4d92c6275575
  - [net-next,2/6] caif_virtio: switch to netif_napi_add_weight()
    https://git.kernel.org/netdev/net-next/c/be8af67fabcb
  - [net-next,3/6] eth: switch to netif_napi_add_weight()
    https://git.kernel.org/netdev/net-next/c/b707b89f7be3
  - [net-next,4/6] r8152: switch to netif_napi_add_weight()
    https://git.kernel.org/netdev/net-next/c/8ded532cd1cb
  - [net-next,5/6] net: virtio: switch to netif_napi_add_weight()
    https://git.kernel.org/netdev/net-next/c/d484735dcf92
  - [net-next,6/6] net: wan: switch to netif_napi_add_weight()
    https://git.kernel.org/netdev/net-next/c/6f83cb8cbfbf

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-05-08 10:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 17:07 [PATCH net-next 0/6] net: switch drivers to netif_napi_add_weight() Jakub Kicinski
2022-05-06 17:07 ` [PATCH net-next 1/6] um: vector: switch " Jakub Kicinski
2022-05-06 17:07   ` Jakub Kicinski
2022-05-06 17:07 ` [PATCH net-next 2/6] caif_virtio: " Jakub Kicinski
2022-05-07  6:55   ` Michael S. Tsirkin
2022-05-06 17:07 ` [PATCH net-next 3/6] eth: " Jakub Kicinski
2022-05-11 17:57   ` Edward Cree
2022-05-11 19:45     ` Jakub Kicinski
2022-05-11 21:02       ` Edward Cree
2022-05-12  7:27         ` Martin Habets
2022-05-06 17:07 ` [PATCH net-next 4/6] r8152: " Jakub Kicinski
2022-05-06 17:07 ` [PATCH net-next 5/6] net: virtio: " Jakub Kicinski
2022-05-07  1:38   ` Xuan Zhuo
2022-05-07  1:38     ` Xuan Zhuo
2022-05-07  3:08   ` Jason Wang
2022-05-07  3:08     ` Jason Wang
2022-05-07  6:55   ` Michael S. Tsirkin
2022-05-07  6:55     ` Michael S. Tsirkin
2022-05-06 17:07 ` [PATCH net-next 6/6] net: wan: " Jakub Kicinski
2022-05-06 17:07   ` Jakub Kicinski
2022-05-08 10:50 ` 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=165200701497.399.16357279983705677828.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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.