From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org
Subject: [ANN] netdev foundation TSC meeting notes - Jun 30th
Date: Tue, 30 Jun 2026 08:25:07 -0700 [thread overview]
Message-ID: <20260630082507.6109b0ca@kernel.org> (raw)
Present: Eric, Jakub, Johannes, Kuniyuki, Simon, Willem, Paolo
Academic Research program
- Revised with:
- Limit of USD 50k/grant
- Simon as email contact (happy for an alias to be created instead)
- Contacted board for funding approval, expect them to meet in
coming weeks to discuss
Netconf:
- on the first day of Netdev 0x1A. 13th July
- Have room for ~20 people
- Finalizing invites today / tomorrow
- Driver upstreaming challenges, some drivers reaching v50
- May be more suitable for a broader discussion / driver BoF?
- Foundation sponsorship for a meal
- Double check what netdev.conf has planned
Logo
- Some delay in paperwork due to the complexity of it
- Now aiming for LPC rather than Netdev
- Comments on the draft sheet
- Mesh in the background would be good to represent networking
- Yes on tux, otherwise the logs are generic, but need a distinct one
- A voting sheeting to grade the suggestions to be circulated
Wireless CI running on netdev foundation infra
reply other threads:[~2026-06-30 15:25 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=20260630082507.6109b0ca@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.