From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org
Subject: [ANN] netdev foundation TSC meeting notes - May 5th
Date: Tue, 5 May 2026 16:07:32 -0700 [thread overview]
Message-ID: <20260505160732.534c947f@kernel.org> (raw)
Present: Eric, Jakub, Johannes, Kuniyuki, Simon, Willem, Paolo
Logo funding approved: aim to use at Netdev 0x1A
Academic Research program
- Academic Research Grant Program proposal drafted and shared with the group
- We should not expect usable patches to be produced
- Plan to set general guidance - Netdev focus - and some example topics
Netconf
- On the first day of Netdev 0x1A. 13th July
- No CFP due to shorter length and collocation with a relevant conference
- Invitations to be sent within the next few weeks
AI Review
- Claude-shiko running, and finding slightly different issues, does
not report preexisting issues
- Hoping to integrate codex once broadly available on Bedrock, as well
- Once we have Claude + Codex the accuracy should be high enough to
start emailing the reviews out automatically (and update the netdev
"FAQ" as appropriate)
reply other threads:[~2026-05-05 23:07 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=20260505160732.534c947f@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