public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Gatis Peisenieks <gatis@mikrotik.com>
Cc: chris.snook@gmail.com, davem@davemloft.net, kuba@kernel.org,
	hkallweit1@gmail.com, jesse.brandeburg@intel.com,
	dchickles@marvell.com, tully@mikrotik.com,
	eric.dumazet@gmail.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/4] add 4 RX/TX queue support for Mikrotik 10/25G NIC
Date: Thu, 27 May 2021 23:10:04 +0000	[thread overview]
Message-ID: <162215700484.22947.15283379800823112526.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210527144423.3395719-1-gatis@mikrotik.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Thu, 27 May 2021 17:44:19 +0300 you wrote:
> More RX/TX queues on a network card help spread the CPU load among
> cores and achieve higher overall networking performance.
> This patch set adds support for 4 RX/TX queues available on
> Mikrotik 10/25G NIC.
> 
> v4:
>     - addressed comments from Jakub Kicinski:
>       - split up the change in more manageable chunks
>       - changed member order in structs for tighter packing
>       - fixed style issues
>     - reverted to calling napi_alloc_skb only from within poll
>       as before
> v3:
>     - fix kernel-doc complaints on comments as pointed out by
>       David Miller
> v2:
>     - rebase on net-next master as requested by David Miller
> 
> [...]

Here is the summary with links:
  - [net-next,v4,1/4] atl1c: detect NIC type early
    https://git.kernel.org/netdev/net-next/c/bf3be85dbe59
  - [net-next,v4,2/4] atl1c: move tx napi into tpd_ring
    https://git.kernel.org/netdev/net-next/c/20a1b6bdca15
  - [net-next,v4,3/4] atl1c: prepare for multiple rx queues
    https://git.kernel.org/netdev/net-next/c/8042824a3c0b
  - [net-next,v4,4/4] atl1c: add 4 RX/TX queue support for Mikrotik 10/25G NIC
    https://git.kernel.org/netdev/net-next/c/057f4af2b171

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



      parent reply	other threads:[~2021-05-27 23:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 14:44 [PATCH net-next v4 0/4] add 4 RX/TX queue support for Mikrotik 10/25G NIC Gatis Peisenieks
2021-05-27 14:44 ` [PATCH net-next v4 1/4] atl1c: detect NIC type early Gatis Peisenieks
2021-05-27 14:44 ` [PATCH net-next v4 2/4] atl1c: move tx napi into tpd_ring Gatis Peisenieks
2021-05-27 14:44 ` [PATCH net-next v4 3/4] atl1c: prepare for multiple rx queues Gatis Peisenieks
2021-05-27 14:44 ` [PATCH net-next v4 4/4] atl1c: add 4 RX/TX queue support for Mikrotik 10/25G NIC Gatis Peisenieks
2021-05-27 23:10 ` 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=162215700484.22947.15283379800823112526.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=chris.snook@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dchickles@marvell.com \
    --cc=eric.dumazet@gmail.com \
    --cc=gatis@mikrotik.com \
    --cc=hkallweit1@gmail.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tully@mikrotik.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