From: patchwork-bot+netdevbpf@kernel.org
To: Justin Lai <justinlai0215@realtek.com>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
horms@kernel.org, jdamato@fastly.com, pkshih@realtek.com,
larry.chiu@realtek.com
Subject: Re: [PATCH net-next v2 0/2] Link NAPI instances to queues and IRQs
Date: Tue, 17 Jun 2025 23:30:56 +0000 [thread overview]
Message-ID: <175020305650.3735715.11500418526187029243.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250616032226.7318-1-justinlai0215@realtek.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 16 Jun 2025 11:22:24 +0800 you wrote:
> This patch series introduces netdev-genl support to rtase, enabling
> user-space applications to query the relationships between IRQs,
> queues, and NAPI instances.
>
> v1 -> v2:
> - Use netif_napi_add_config() to support persistent NAPI configuration.
> - Use enum netdev_queue_type instead of driver-specific values.
> - Rename ring_type to type.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] rtase: Link IRQs to NAPI instances
https://git.kernel.org/netdev/net-next/c/9f611bfd1011
- [net-next,v2,2/2] rtase: Link queues to NAPI instances
https://git.kernel.org/netdev/net-next/c/8d672a3e51ad
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:[~2025-06-17 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 3:22 Justin Lai
2025-06-16 3:22 ` [PATCH net-next v2 1/2] rtase: Link IRQs to NAPI instances Justin Lai
2025-06-16 15:42 ` Joe Damato
2025-06-17 7:20 ` Justin Lai
2025-06-16 3:22 ` [PATCH net-next v2 2/2] rtase: Link queues " Justin Lai
2025-06-16 15:46 ` Joe Damato
2025-06-17 23:30 ` 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=175020305650.3735715.11500418526187029243.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=justinlai0215@realtek.com \
--cc=kuba@kernel.org \
--cc=larry.chiu@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkshih@realtek.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
all inboxes | Powered by JetHome®