From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org
Subject: [ANN] netdev foundation TSC meeting notes - Oct 22nd
Date: Tue, 20 Oct 2026 09:44:18 -0700 [thread overview]
Message-ID: <20261020094418.1cf06514@kernel.org> (raw)
Present: Andrew, Jakub, Johannes, Kuniyuki, Paolo, Willem, Simon
Guest: Matthieu
Presentation by Matthieu Baerts
- Update on 6 months of work
1. Lab maintenance
2. New features
- https://docs.google.com/document/d/1XOP7DGSWSyEYR1u4plxIxck9FrnB54MTvnzYRE7y1-I/edit?usp=sharing
Lab update
- Have PO for next 2 HW testing machines, will submit order today
- Need to purchase cables separately
Academic research program
- CFP now open: https://sessionize.com/netdev-foundation-call-for-proposals/
Merge window
- May run for three weeks; if so, Netdev may reopen sooner, after 2 weeks
Patch Review
- Jakub is concerned about patch merging in his absence
(gotta take a break sometimes!)
- Some discussion about extra help
- Some discussion of AI/bot applying patches that are Acked and green
AI
- Discussion of CC Sashiko emails: list + author
- Fix clarification bot (series info)
- Anecdotally seems to be working
- Johannes feels the providence requested is important in the light
of LLM assisted patches Test acceptance criteria
- Testing
- Before we begged for tests
- Now we are overwhelmed by AI generated tests
- Where to draw the line? What is of value?
- An option is to add test-specific prompts to Sashiko (NIPA)
Patch “Takeover”
- Jakub considers adding policy welcoming maintainers taking over
submissions for LLM fixes E.g. for problems highlighted by Sashiko
- Needs some nuance for non–drive-by case
reply other threads:[~2026-10-20 16:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261020094418.1cf06514@kernel.org \
--to=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