From: Simon Horman <horms@kernel.org>
To: David 'equinox' Lamparter <equinox@diac24.net>
Cc: pabeni@redhat.com, kuba@kernel.org, idosch@nvidia.com,
dsahern@kernel.org, davem@davemloft.net, edumazet@google.com,
corbet@lwn.net, skhan@linuxfoundation.org, fmancera@suse.de,
lorenzo@google.com, maze@google.com, netdev@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
furry13@gmail.com
Subject: Re: [PATCH net-next 7/9] net/ipv6: support RFC6724 rule 5.5 via subtrees
Date: Wed, 22 Jul 2026 12:17:18 +0100 [thread overview]
Message-ID: <20260722111718.GB418547@horms.kernel.org> (raw)
In-Reply-To: <al-EPInqzpka3zi6@eidolon.nox.tf>
On Tue, Jul 21, 2026 at 04:37:48PM +0200, David 'equinox' Lamparter wrote:
> Hi Simon,
>
>
> On Tue, Jul 21, 2026 at 02:50:14PM +0100, Simon Horman wrote:
> > This is an AI-generated review of your patch. The human sending this
> > email has considered the AI review valid, or at least plausible.
> > https://sashiko.dev/#/patchset/20260714094030.136317-2-equinox@diac24.net?part=7
>
> Thanks for forwarding the Sashiko reports, I was already aware of them & am almost done addressing them. The external nexthop stuff is "inapplicable" since the kernel refuses subtree routes with nexthop objects, but I've made that more explicit. Other than that it's relatively simple oversights on my end.
>
> I just need to make it pretty & hit send, I'll hopefully get to it tomorrow.
Thanks, much appreciated on all counts.
next prev parent reply other threads:[~2026-07-22 11:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 9:40 [PATCH net-next 0/9] RFC 6724 rule 5.5 support David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 1/9] net/ipv6: fix lookup for ::/0 (non-)subtree route David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 2/9] net/ipv6: flatten ip6_route_get_saddr David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 3/9] net/ipv6: create ipv6_fl_get_saddr David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 4/9] net/ipv6: use ipv6_fl_get_saddr in output David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 5/9] net/ipv6: drop ip6_route_get_saddr David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 6/9] net/ipv6: flip IPV6_SUBTREES default to Y David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 7/9] net/ipv6: support RFC6724 rule 5.5 via subtrees David 'equinox' Lamparter
2026-07-21 13:50 ` Simon Horman
2026-07-21 14:37 ` David 'equinox' Lamparter
2026-07-22 11:17 ` Simon Horman [this message]
2026-07-14 9:40 ` [PATCH net-next 8/9] selftests: net: RFC6724 rule 5.5 tests David 'equinox' Lamparter
2026-07-21 13:50 ` Simon Horman
2026-07-14 9:40 ` [PATCH net-next 9/9] net: document RFC6724 rule 5.5 implementation David 'equinox' Lamparter
2026-07-14 13:01 ` Jonathan Corbet
2026-07-14 17:16 ` David 'equinox' Lamparter
2026-07-14 17:31 ` Jonathan Corbet
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=20260722111718.GB418547@horms.kernel.org \
--to=horms@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=equinox@diac24.net \
--cc=fmancera@suse.de \
--cc=furry13@gmail.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lorenzo@google.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.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