From: Simon Horman <horms@kernel.org>
To: Patrick Rohr <prohr@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
"Linux Network Development Mailing List" <netdev@vger.kernel.org>,
"Maciej Żenczykowski" <maze@google.com>,
"Lorenzo Colitti" <lorenzo@google.com>,
"David Lamparter" <equinox@opensourcerouting.org>
Subject: Re: [PATCH net-next] Add support for PIO p flag
Date: Sun, 28 Jul 2024 08:17:46 +0100 [thread overview]
Message-ID: <20240728071746.GB1625564@kernel.org> (raw)
In-Reply-To: <20240726102318.GN97837@kernel.org>
On Fri, Jul 26, 2024 at 11:23:18AM +0100, Simon Horman wrote:
> On Thu, Jul 25, 2024 at 06:06:29PM -0700, Patrick Rohr wrote:
> > draft-ietf-6man-pio-pflag is adding a new flag to the Prefix Information
> > Option to signal the pd-per-device addressing mechanism.
> >
> > When accept_pio_pflag is enabled, the presence of the p-flag will cause
> > an a flag in the same PIO to be ignored.
> >
> > An automated test has been added in Android (r.android.com/3195335) to
> > go along with this change.
> >
> > Cc: Maciej Żenczykowski <maze@google.com>
> > Cc: Lorenzo Colitti <lorenzo@google.com>
> > Cc: David Lamparter <equinox@opensourcerouting.org>
> > Signed-off-by: Patrick Rohr <prohr@google.com>
>
> Hi Patrick,
>
> This is not a full review, and as per the form letter below,
> net-next is closed, so you'd be best to repost.
> But I will offer some very minor review in the meantime.
>
> Firstly, please seed the CC list for Networking patches
> using get_maintainers.pl --git-min-percent 25 this.patch
>
> Secondly, as noted inline, there are two cases of
> mixed of tabs and spaces used for indenting in this patch.
>
> ## Form letter - net-next-closed
>
> The merge window for v6.11 has begun and therefore net-next is closed
> for new drivers, features, code refactoring and optimizations.
> We are currently accepting bug fixes only.
>
> Please repost when net-next reopens after 15th July
Sorry, I'm not sure why I wrote the 15th, I meant the 29th.
>
> RFC patches sent for review only are welcome at any time.
>
> See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
...
next prev parent reply other threads:[~2024-07-28 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 1:06 [PATCH net-next] Add support for PIO p flag Patrick Rohr
2024-07-26 10:23 ` Simon Horman
2024-07-28 7:17 ` Simon Horman [this message]
2024-07-29 14:49 ` Patrick Rohr
2024-07-29 17:22 ` Maciej Żenczykowski
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=20240728071746.GB1625564@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=equinox@opensourcerouting.org \
--cc=lorenzo@google.com \
--cc=maze@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).