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

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

[Uwe Kleine-König]

Documentation/process/maintainer-netdev.rst was adapted in commit
524500873802 ("docs: netdev: update the netdev infra URLs") to use
netdev.bots.linux.dev as base for (among others) the "is net-next open?"
tracker. Adapt the bpf documentation accordingly.

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>
---
Hello,

I was unsure if I should delay sending out that patch, because it might
be considered a fix and I could have talked me out of sending during the
merge window by claiming that the (old) URL didn't tell me to delay :-)

Anyhow, it's not very urgent (I think), so I waited until -rc1.

Best regards
Uwe

 Documentation/bpf/bpf_devel_QA.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/bpf/bpf_devel_QA.rst b/Documentation/bpf/bpf_devel_QA.rst
index 4729efd657c3..7f1531f0848c 100644
--- a/Documentation/bpf/bpf_devel_QA.rst
+++ b/Documentation/bpf/bpf_devel_QA.rst
@@ -243,7 +243,7 @@ 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
+  https://netdev.bots.linux.dev/net-next.html
 
 Q: Verifier changes and test cases
 ----------------------------------

base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
-- 
2.56.0.rc1

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

[bot+bpf-ci]

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

> bpf: Use "new" URL to show if net-next is open

TL;DR: Nit in the docs URL update: the unchanged text still credits David S.
Miller for the status page, which may be inaccurate for the new
netdev.bots.linux.dev host; consider rewording or noting it in the changelog.

> diff --git a/Documentation/bpf/bpf_devel_QA.rst b/Documentation/bpf/bpf_devel_QA.rst
> index 4729efd657c3..7f1531f0848c 100644
> --- a/Documentation/bpf/bpf_devel_QA.rst
> +++ b/Documentation/bpf/bpf_devel_QA.rst
> @@ -243,7 +243,7 @@ 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
> +  https://netdev.bots.linux.dev/net-next.html

This isn't a bug, but the sentence introducing the URL is unchanged:

  page run by David S. Miller on net-next that provides guidance:

That attribution matched the old ~davem page on vger.kernel.org.  Is it
still accurate for the new host?

Commit 524500873802 ("docs: netdev: update the netdev infra URLs"), which
the changelog cites, describes netdev.bots.linux.dev as a new DNS entry for
the netdev infrastructure, and Documentation/process/maintainer-netdev.rst
refers to the same page without naming David S. Miller.

Should the attribution be dropped or reworded, for example "a status page
maintained by the netdev infrastructure", or should the changelog mention
that the page is still run by David S. Miller?


---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md

CI run summary: https://github.com/kernel-patches/bpf/actions/runs/41436735330

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

[Alexei Starovoitov]

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.

pw-bot: cr

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

[Uwe Kleine-König]

[-- 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 --]

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

[Alexei Starovoitov]

On Mon Nov 2, 2026 at 5:51 PM UTC, Uwe Kleine-König wrote:
> 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?

Pls send a patch.