From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, willemb@google.com, netdev@vger.kernel.org,
yoshfuji@linux-ipv6.org, dsahern@kernel.org
Subject: Re: [PATCH net 0/2] udp6: allow SO_MARK ctrl msg to affect routing
Date: Mon, 01 Nov 2021 13:20:08 +0000 [thread overview]
Message-ID: <163577280801.31246.523680560913994797.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211029155135.468098-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 29 Oct 2021 08:51:33 -0700 you wrote:
> Hi!
>
> Looks like SO_MARK from cmsg does not affect routing policy.
> This seems accidental.
>
> I opted for net because of the discrepancy between IPv4
> and IPv6, but it never worked and doesn't cause crashes..
>
> [...]
Here is the summary with links:
- [net,1/2] udp6: allow SO_MARK ctrl msg to affect routing
https://git.kernel.org/netdev/net/c/42dcfd850e51
- [net,2/2] selftests: udp: test for passing SO_MARK as cmsg
https://git.kernel.org/netdev/net/c/b0ced8f290fb
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:[~2021-11-01 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 15:51 [PATCH net 0/2] udp6: allow SO_MARK ctrl msg to affect routing Jakub Kicinski
2021-10-29 15:51 ` [PATCH net 1/2] " Jakub Kicinski
2021-10-29 18:22 ` David Ahern
2021-10-30 1:23 ` Willem de Bruijn
2021-10-29 15:51 ` [PATCH net 2/2] selftests: udp: test for passing SO_MARK as cmsg Jakub Kicinski
2021-10-29 18:24 ` David Ahern
2021-10-30 1:14 ` Willem de Bruijn
2021-11-01 13:20 ` 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=163577280801.31246.523680560913994797.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
--cc=yoshfuji@linux-ipv6.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).