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 v5 0/3] ioam6: netlink multicast event
Date: Wed, 28 Feb 2024 11:20:34 +0000 [thread overview]
Message-ID: <170911923407.32073.2495064703412581430.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240226131412.10214-1-justin.iurman@uliege.be>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 26 Feb 2024 14:14:09 +0100 you wrote:
> v5:
> - remove the "must be the destination" check before sending an ioam6
> event
> v4:
> - rebase on top of net merge
> v3:
> - patchset was mistakenly superseded due to same cover title used for
> iproute2-next equivalent patch -> resend (renamed)
> v2:
> - fix warnings
>
> [...]
Here is the summary with links:
- [net-next,v5,1/3] uapi: ioam6: API for netlink multicast events
https://git.kernel.org/netdev/net-next/c/5fa918a33563
- [net-next,v5,2/3] net: ioam6: multicast event
https://git.kernel.org/netdev/net-next/c/67c8e4bb4f54
- [net-next,v5,3/3] net: exthdrs: ioam6: send trace event
https://git.kernel.org/netdev/net-next/c/f655c78d6225
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-02-28 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 13:14 [PATCH net-next v5 0/3] ioam6: netlink multicast event Justin Iurman
2024-02-26 13:14 ` [PATCH net-next v5 1/3] uapi: ioam6: API for netlink multicast events Justin Iurman
2024-02-26 13:14 ` [PATCH net-next v5 2/3] net: ioam6: multicast event Justin Iurman
2024-02-26 13:14 ` [PATCH net-next v5 3/3] net: exthdrs: ioam6: send trace event Justin Iurman
2024-02-28 11: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=170911923407.32073.2495064703412581430.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