From: patchwork-bot+netdevbpf@kernel.org
To: Justin Iurman <justin.iurman@uliege.be>
Cc: netdev@vger.kernel.org, davem@davemloft.net, dsahern@kernel.org,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/2] net: ipv6: ioam6: introduce tunsrc
Date: Thu, 22 Aug 2024 09:00:27 +0000 [thread overview]
Message-ID: <172431722701.2256827.13061551625019118054.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240817131818.11834-1-justin.iurman@uliege.be>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 17 Aug 2024 15:18:16 +0200 you wrote:
> This series introduces a new feature called "tunsrc" (just like seg6
> already does).
>
> v3:
> - address Jakub's comments
>
> v2:
> - add links to performance result figures (see patch#2 description)
> - move the ipv6_addr_any() check out of the datapath
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: ipv6: ioam6: code alignment
https://git.kernel.org/netdev/net-next/c/924b8bea870b
- [net-next,v3,2/2] net: ipv6: ioam6: new feature tunsrc
https://git.kernel.org/netdev/net-next/c/273f8c142003
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:[~2024-08-22 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 13:18 [PATCH net-next v3 0/2] net: ipv6: ioam6: introduce tunsrc Justin Iurman
2024-08-17 13:18 ` [PATCH net-next v3 1/2] net: ipv6: ioam6: code alignment Justin Iurman
2024-08-17 13:18 ` [PATCH net-next v3 2/2] net: ipv6: ioam6: new feature tunsrc Justin Iurman
2024-08-22 8:44 ` Paolo Abeni
2024-08-22 12:46 ` Justin Iurman
2024-08-22 9:00 ` 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=172431722701.2256827.13061551625019118054.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=justin.iurman@uliege.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox