All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org
Cc: Simon Horman <horms@kernel.org>
Subject: [ANN] netdev foundation TSC meeting notes - Nov 25th
Date: Wed, 26 Nov 2025 14:17:00 -0800	[thread overview]
Message-ID: <20251126141700.25c097cb@kernel.org> (raw)

Hi!

The netdev foundation TSC meet on Nov 25th.

Lab update
 - NF machines are not racked and running (replacement of existing NIPA setup)
   - HW meets our needs, so order for a couple more machines was submitted
 - DNS entries and certs added
 - Migrated build and VM/ksft testing; control and DB bits still remaining
   - build is noticeably faster which is nice
     - old AWS build system has been shut down
   - kselftests are flaky in new ways on new setup (virt-X remotes)
     - we need to stabilize them before shutting down the AWS system
 - SSH access granted to a few folks but in general pending appropriate
   automation

Funding: PHY Testing SoW
 - Approved.
 - 7 yes from 8 present from 9 members
 - Quorum is 50% (reached); Votes are made by simple majority (also reached)	

New project suggestion:
 - Paolo suggests improving / re-implementing AF_ROSE
 - Simon will create ticket

AI review-prompts now live in netdev CI, for now reporting to patchwork
only as "warning". Need more confidence before email reporting.

LPC: should we have a “maintainer talk / Q&A”? 30min in the AM?
 - Will hold before official start at 10am
 - Paolo will “squash” schedule into remaining time

Next meeting canceled due to LPC and Xmas break.

             reply	other threads:[~2025-11-26 22:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26 22:17 Jakub Kicinski [this message]
2025-11-27  4:24 ` [ANN] netdev foundation TSC meeting notes - Nov 25th Cong Wang

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=20251126141700.25c097cb@kernel.org \
    --to=kuba@kernel.org \
    --cc=horms@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.