From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, dsahern@gmail.com,
stephen@networkplumber.org, petrm@nvidia.com, gnault@redhat.com
Subject: Re: [PATCH iproute2-next v2 0/3] Add flow label support to ip-rule and route get
Date: Wed, 01 Jan 2025 01:30:33 +0000 [thread overview]
Message-ID: <173569503352.1658795.12413555846627392455.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241230085810.87766-1-idosch@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Mon, 30 Dec 2024 10:58:07 +0200 you wrote:
> Add IPv6 flow label support to ip-rule and route get requests following
> kernel support that was added in kernel commit 6b3099ebca13 ("Merge
> branch 'net-fib_rules-add-flow-label-selector-support'").
>
> v2:
> * Remove new line from invarg() invocations.
>
> [...]
Here is the summary with links:
- [iproute2-next,v2,1/3] Sync uAPI headers
(no matching commit)
- [iproute2-next,v2,2/3] ip: route: Add IPv6 flow label support
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=35ae138e2c94
- [iproute2-next,v2,3/3] iprule: Add flow label support
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=0bd19d4645ce
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:[~2025-01-01 1:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 8:58 [PATCH iproute2-next v2 0/3] Add flow label support to ip-rule and route get Ido Schimmel
2024-12-30 8:58 ` [PATCH iproute2-next v2 1/3] Sync uAPI headers Ido Schimmel
2024-12-30 8:58 ` [PATCH iproute2-next v2 2/3] ip: route: Add IPv6 flow label support Ido Schimmel
2024-12-31 0:49 ` Stephen Hemminger
2024-12-31 7:13 ` Ido Schimmel
2024-12-30 8:58 ` [PATCH iproute2-next v2 3/3] iprule: Add " Ido Schimmel
2025-01-01 1:30 ` 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=173569503352.1658795.12413555846627392455.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@gmail.com \
--cc=gnault@redhat.com \
--cc=idosch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--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 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).