From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, dsahern@kernel.org,
shuah@kernel.org, idosch@nvidia.com,
Jacques.De.Laval@westermo.com
Subject: Re: [PATCH net-next 0/3] net: Allow changing IPv4 address protocol
Date: Thu, 23 Mar 2023 08:40:20 +0000 [thread overview]
Message-ID: <167956082033.32268.14255202723457599070.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1679399108.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 21 Mar 2023 12:51:58 +0100 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.
>
> When IP address protocol field was added in commit 47f0bd503210 ("net: Add
> new protocol attribute to IP addresses"), the semantics included the
> ability to change the protocol for IPv6 addresses, but not for IPv4
> addresses. It seems this was not deliberate, but rather by accident.
>
> [...]
Here is the summary with links:
- [net-next,1/3] net: ipv4: Allow changing IPv4 address protocol
https://git.kernel.org/netdev/net-next/c/5c4a9aa856c7
- [net-next,2/3] selftests: rtnetlink: Make the set of tests to run configurable
https://git.kernel.org/netdev/net-next/c/ecb3c1e675c7
- [net-next,3/3] selftests: rtnetlink: Add an address proto test
https://git.kernel.org/netdev/net-next/c/6a414fd77f61
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-23 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 11:51 [PATCH net-next 0/3] net: Allow changing IPv4 address protocol Petr Machata
2023-03-21 11:51 ` [PATCH net-next 1/3] net: ipv4: " Petr Machata
2023-03-22 2:28 ` David Ahern
2023-03-21 11:52 ` [PATCH net-next 2/3] selftests: rtnetlink: Make the set of tests to run configurable Petr Machata
2023-03-21 11:52 ` [PATCH net-next 3/3] selftests: rtnetlink: Add an address proto test Petr Machata
2023-03-22 2:30 ` David Ahern
2023-03-23 8: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=167956082033.32268.14255202723457599070.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Jacques.De.Laval@westermo.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=shuah@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).