From: patchwork-bot+netdevbpf@kernel.org
To: Gur Stavi <gur.stavi@huawei.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, gongfan1@huawei.com
Subject: Re: [PATCH net-next v3 0/3] hinic3: queue_api related fixes
Date: Tue, 10 Jun 2025 23:39:43 +0000 [thread overview]
Message-ID: <174959878373.2630805.15421085974228981333.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1749038081.git.gur.stavi@huawei.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 9 Jun 2025 18:07:51 +0300 you wrote:
> This patch series contains improvement to queue_api and 2 queue_api
> related patches to the hinic3 driver.
>
> Changes:
>
> v1: http://lore.kernel.org/netdev/cover.1747824040.git.gur.stavi@huawei.com
>
> [...]
Here is the summary with links:
- [net-next,v3,1/3] queue_api: add subqueue variant netif_subqueue_sent
https://git.kernel.org/netdev/net-next/c/2bc64b89c4c4
- [net-next,v3,2/3] hinic3: use netif_subqueue_sent api
https://git.kernel.org/netdev/net-next/c/eb89bc3744f3
- [net-next,v3,3/3] hinic3: remove tx_q name collision hack
https://git.kernel.org/netdev/net-next/c/48b9ce0a7c72
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-10 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 15:07 [PATCH net-next v3 0/3] hinic3: queue_api related fixes Gur Stavi
2025-06-09 15:07 ` [PATCH net-next v3 1/3] queue_api: add subqueue variant netif_subqueue_sent Gur Stavi
2025-06-09 15:07 ` [PATCH net-next v3 2/3] hinic3: use netif_subqueue_sent api Gur Stavi
2025-06-09 15:07 ` [PATCH net-next v3 3/3] hinic3: remove tx_q name collision hack Gur Stavi
2025-06-10 23:39 ` 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=174959878373.2630805.15421085974228981333.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gongfan1@huawei.com \
--cc=gur.stavi@huawei.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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.