From: patchwork-bot+netdevbpf@kernel.org
To: Justin Iurman <justin.iurman@uliege.be>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, stephen@networkplumber.org
Subject: Re: [PATCH iproute2-next 1/2] Add support for the IOAM insertion frequency
Date: Thu, 10 Feb 2022 18:10:10 +0000 [thread overview]
Message-ID: <164451661000.28542.11297772284276369342.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220205155208.22531-2-justin.iurman@uliege.be>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Sat, 5 Feb 2022 16:52:07 +0100 you wrote:
> This patch adds support for the IOAM insertion frequency by introducing
> a new parameter "freq". The expected value is "k/n", see the patchset
> description for more details.
>
> Signed-off-by: Justin Iurman <justin.iurman@uliege.be>
> ---
> ip/iproute_lwtunnel.c | 69 +++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 67 insertions(+), 2 deletions(-)
Here is the summary with links:
- [iproute2-next,1/2] Add support for the IOAM insertion frequency
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=8908cb25711e
- [iproute2-next,2/2] Update documentation
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=ff14875e9d77
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-02-10 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 15:52 [PATCH iproute2-next 0/2] Support for the IOAM insertion frequency Justin Iurman
2022-02-05 15:52 ` [PATCH iproute2-next 1/2] Add support " Justin Iurman
2022-02-10 18:10 ` patchwork-bot+netdevbpf [this message]
2022-02-05 15:52 ` [PATCH iproute2-next 2/2] Update documentation Justin Iurman
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=164451661000.28542.11297772284276369342.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 \
--cc=stephen@networkplumber.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 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.