From: patchwork-bot+netdevbpf@kernel.org
To: Davide Caratti <dcaratti@redhat.com>
Cc: kuba@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, jhs@mojatatu.com,
victor@mojatatu.com, jiri@resnulli.us, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/3] netdevsim: support ETS offload
Date: Sat, 21 Mar 2026 03:20:32 +0000 [thread overview]
Message-ID: <177406323203.2737822.1727843516019475591.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1773945414.git.dcaratti@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 19 Mar 2026 19:40:53 +0100 you wrote:
> - patch 1 moves netdevsim tc offloads to a dedicated file
> - patch 2 enables ETS offload on netdevsim
> - patch 3 is a tdc test for ets offload on netdevsim
>
> v2: don't use x-macro (Jakub Kicinski)
> v3: move function declaration from the bottom of netdevsim.h (Jakub Kicinski)
> v4: explicit path for ethtool in tdc_config.py (Victor Nogueira)
>
> [...]
Here is the summary with links:
- [net-next,v4,1/3] netdevsim: move TC offload code to a dedicated file
https://git.kernel.org/netdev/net-next/c/544921efd4e4
- [net-next,v4,2/3] netdevsim: support tc-ets offload
https://git.kernel.org/netdev/net-next/c/abdf5133bfa1
- [net-next,v4,3/3] tc-testing: add a test case for ETS offload
https://git.kernel.org/netdev/net-next/c/5754a1c9f9b6
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:[~2026-03-21 3:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 18:40 [PATCH net-next v4 0/3] netdevsim: support ETS offload Davide Caratti
2026-03-19 18:40 ` [PATCH net-next v4 1/3] netdevsim: move TC offload code to a dedicated file Davide Caratti
2026-03-19 18:40 ` [PATCH net-next v4 2/3] netdevsim: support tc-ets offload Davide Caratti
2026-03-19 18:40 ` [PATCH net-next v4 3/3] tc-testing: add a test case for ETS offload Davide Caratti
2026-03-21 3:20 ` 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=177406323203.2737822.1727843516019475591.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=victor@mojatatu.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