From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: netdev@vger.kernel.org, dsahern@gmail.com, stephen@networkplumber.org
Subject: Re: [PATCH iproute2-next 0/2] ip: Support IP address protocol
Date: Thu, 30 Mar 2023 16:00:18 +0000 [thread overview]
Message-ID: <168019201884.15770.16440073183438285696.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1679933258.git.petrm@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Mon, 27 Mar 2023 18:12:04 +0200 you wrote:
> IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
> provenance of the IP address. The attribute is modeled after ip route
> protocols, and essentially allows the administrator or userspace stack to
> tag addresses in some way that makes sense to the actor in question.
> Support for this feature was merged with commit 47f0bd503210 ("net: Add new
> protocol attribute to IP addresses"), for kernel 5.18.
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] ip: Support IP address protocol
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=bdb8d8549ed9
- [iproute2-next,2/2] man: man8: Add man page coverage for "ip address add ... proto"
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=1fbb61058d34
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:[~2023-03-30 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 16:12 [PATCH iproute2-next 0/2] ip: Support IP address protocol Petr Machata
2023-03-30 16: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=168019201884.15770.16440073183438285696.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@gmail.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 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.