public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Dawid Osuchowski <linux@osuchow.ski>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org
Subject: Re: [ANN] netdev development stats for 7.0 (and some AI review thoughts)
Date: Thu, 19 Feb 2026 10:47:05 +0100	[thread overview]
Message-ID: <55190384-e06a-45ef-ba7c-55d341e93e83@osuchow.ski> (raw)
In-Reply-To: <20260217141500.00c3fa2d@kernel.org>

On 17/02/2026 23:15, Jakub Kicinski wrote:
> On Mon, 16 Feb 2026 00:31:08 +0100 Dawid Osuchowski wrote:
>>> One more note on testing, we have completed the migration of NIPA
>>> to netdev foundation machines. Due to DRAM shortage, however,
>>> the shipment of additional machines is delayed.
>>
>> Just something I noticed that might be connected to this is that the
>> links to "Raw output" in these announcements broke for each previous
>> message you posted.
>>
>> It is possible to use the new link convention/format:
>>
>> 	Raw output: https://netdev.bots.linux.dev/ml-stats/stats-7.0
>>
>> to go back as far as 6.18 stats e.g.:
>>
>> 	https://netdev.bots.linux.dev/ml-stats/stats-6.18
>>
>> but beyond that (6.17 and older) it doesn't work. The "old" nipa links:
>>
>> 	Raw output: https://netdev.bots.linux.dev/static/nipa/stats-6.19/stdout
>>
>> are completely broken.
> 
> Yup, this is due to the NIPA migration from Meta systems to netdev
> foundation machines. I can regenerate the outputs if you need them
> (modulo the JSON format changing since), LMK if and how far back.

I don't need them, just noticed the gap and reported it, as I thought 
you might've not been aware.

> I did copy the "time based" stats from old machines (3mo, 6mo etc) FWIW:
> https://netdev.bots.linux.dev/ml-stats/
> which I suspect to be more useful for actionable tracking of activity
> than the release-by-release. Release stats are mostly an excuse to send
> an email to the list and thank people :)

Understood, in that case my response above still holds true. For myself 
I don't need anything more, but other folks might want/need them for 
some purpose. If they do I guess they will let you know one way or 
another :)

>> P.S. I am using a freshly setup email client on a new machine so
>> apologies if the formatting is wrong on my end. I did send this message
>> to myself for testing and I think it's okay, but I might be missing
>> something :)
> 
> Looks fine :)

Thanks for confirming!
Dawid


      reply	other threads:[~2026-02-19  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 20:42 [ANN] netdev development stats for 7.0 (and some AI review thoughts) Jakub Kicinski
2026-02-15 23:31 ` Dawid Osuchowski
2026-02-17 22:15   ` Jakub Kicinski
2026-02-19  9:47     ` Dawid Osuchowski [this message]

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=55190384-e06a-45ef-ba7c-55d341e93e83@osuchow.ski \
    --to=linux@osuchow.ski \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.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