From: patchwork-bot+netdevbpf@kernel.org
To: Justin Iurman <justin.iurman@uliege.be>
Cc: netdev@vger.kernel.org, dsahern@kernel.org
Subject: Re: [PATCH iproute2-next 0/3] multicast event support for ioam6
Date: Sun, 03 Mar 2024 22:40:28 +0000 [thread overview]
Message-ID: <170950562835.16991.13440473552331986103.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240222154539.19904-1-justin.iurman@uliege.be>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Thu, 22 Feb 2024 16:45:36 +0100 you wrote:
> Add support for ioam multicast events via a new command: ip ioam
> monitor.
>
> Justin Iurman (3):
> uapi: ioam6: update uapi based on net-next
> ip: ioam6: add monitor command
> man8: ioam: add doc for monitor command
>
> [...]
Here is the summary with links:
- [iproute2-next,1/3] uapi: ioam6: update uapi based on net-next
(no matching commit)
- [iproute2-next,2/3] ip: ioam6: add monitor command
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=ae5c6f9b0391
- [iproute2-next,3/3] man8: ioam: add doc for monitor command
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=94107bba2456
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-03-03 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 15:45 [PATCH iproute2-next 0/3] multicast event support for ioam6 Justin Iurman
2024-02-22 15:45 ` [PATCH iproute2-next 1/3] uapi: ioam6: update uapi based on net-next Justin Iurman
2024-02-22 15:45 ` [PATCH iproute2-next 2/3] ip: ioam6: add monitor command Justin Iurman
2024-02-22 15:45 ` [PATCH iproute2-next 3/3] man8: ioam: add doc for " Justin Iurman
2024-03-03 22:40 ` 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=170950562835.16991.13440473552331986103.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@kernel.org \
--cc=justin.iurman@uliege.be \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).