Re: [PATCH bpf-next] bpf: Use "new" URL to show if net-next is open

["Uwe Kleine-König" <u.kleine-koenig@baylibre.com>]

[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]

Hello,

On Mon, Nov 02, 2026 at 04:50:37PM +0000, Alexei Starovoitov wrote:
> On Mon, Nov 02, 2026 at 03:15 AM Uwe Kleine-König <u.kleine-koenig@baylibre.com> wrote:
> >  For non-subscribers to kernel mailing lists, there is also a status
> >  page run by David S. Miller on net-next that provides guidance:
> >
> > -  http://vger.kernel.org/~davem/net-next.html
> > +  https://netdev.bots.linux.dev/net-next.html
> 
> The link is not the only stale part. The whole paragraph is wrong.
> We apply patches during the merge window too.
> 
> diff --git a/Documentation/bpf/bpf_devel_QA.rst b/Documentation/bpf/bpf_devel_QA.rst
> index 4729efd..f6b9533 100644
> --- a/Documentation/bpf/bpf_devel_QA.rst
> +++ b/Documentation/bpf/bpf_devel_QA.rst
> @@ -231,19 +231,9 @@ load or urgency.
> 
>  Q: Are patches applied to bpf-next when the merge window is open?
>  -----------------------------------------------------------------
> -A: For the time when the merge window is open, bpf-next will not be
> -processed. This is roughly analogous to net-next patch processing,
> -so feel free to read up on the netdev docs at
> -Documentation/process/maintainer-netdev.rst about further details.
> -
> -During those two weeks of merge window, we might ask you to resend
> -your patch series once bpf-next is open again. Once Linus released
> -a ``v*-rc1`` after the merge window, we continue processing of bpf-next.
> -
> -For non-subscribers to kernel mailing lists, there is also a status
> -page run by David S. Miller on net-next that provides guidance:
> -
> -  http://vger.kernel.org/~davem/net-next.html
> +A: Yes.

Even better. Do you care to get this change in then?

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]