From: Jakub Kicinski <kuba@kernel.org>
To: David Lamparter <equinox@diac24.net>
Cc: netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Lorenzo Colitti <lorenzo@google.com>,
Patrick Rohr <prohr@google.com>
Subject: Re: [PATCH net-next v2 0/4] net/ipv6: RFC6724 rule 5.5 preparations
Date: Fri, 25 Jul 2025 17:39:58 -0700 [thread overview]
Message-ID: <20250725173958.4d77792d@kernel.org> (raw)
In-Reply-To: <20250724150042.6361-1-equinox@diac24.net>
On Thu, 24 Jul 2025 17:00:37 +0200 David Lamparter wrote:
> let's try this again, this time without accidentally shadowing the 'err'
> variable. Sigh. (Apologies for the immediate v2.)
>
> following 4 patches are preparations for RFC6724 (IPv6 source address
> selection) rule 5.5, which says "prefer addresses announced by the
> router you're using". The changes here just pass down the route into
> the source address selection code, it's not used for anything yet.
> (Any change of behavior from these patches is a mistake on my end.)
Would you mind reposting after the merge window (>= Aug 11th)?
I'm trying to wrap up our net-next PR for 6.17 today and
these changes don't look obvious enough for me to tackle
after 6 hours of staring at diffs.. ;$
--
pw-bot: defer
next prev parent reply other threads:[~2025-07-26 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 15:00 [PATCH net-next v2 0/4] net/ipv6: RFC6724 rule 5.5 preparations David Lamparter
2025-07-24 15:00 ` [PATCH net-next v2 1/4] net/ipv6: flatten ip6_route_get_saddr David Lamparter
2025-07-24 15:00 ` [PATCH net-next v2 2/4] net/ipv6: create ipv6_fl_get_saddr David Lamparter
2025-07-24 15:00 ` [PATCH net-next v2 3/4] net/ipv6: use ipv6_fl_get_saddr in output David Lamparter
2025-07-24 15:00 ` [PATCH net-next v2 4/4] net/ipv6: drop ip6_route_get_saddr David Lamparter
2025-07-26 0:39 ` Jakub Kicinski [this message]
2025-07-26 11:29 ` [PATCH net-next v2 0/4] net/ipv6: RFC6724 rule 5.5 preparations David Lamparter
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=20250725173958.4d77792d@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=equinox@diac24.net \
--cc=lorenzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=prohr@google.com \
/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).