netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org
Cc: Jiri Pirko <jiri@resnulli.us>, Rahul Rameshbabu <rrameshbabu@nvidia.com>
Subject: Re: [ANN] netdev call - Dec 4th
Date: Tue, 5 Dec 2023 10:16:49 -0800	[thread overview]
Message-ID: <20231205101649.4403be0d@kernel.org> (raw)
In-Reply-To: <20231204100735.18e622b2@kernel.org>

On Mon, 4 Dec 2023 10:07:35 -0800 Jakub Kicinski wrote:
> I, again, have a minor update on the CI. I'd also like to talk about
> end-of-year shutdown. Please suggest / come to the meeting with
> other topics!

Meeting notes:

 * Testing:
   * The testing repo is now fully operational, branches are combined
     net + net-next + all cleanly building patches from patchwork.
   * next step for Jakub is to use it to run slow build tests (htmldocs,
     cocci)
   * Jesse trying to get GitHub runner targeting Intel-internal machines
   * reach out to Jesse / Jakub for access to the GitHub

 * Winter Holidays shutdown:
   * Anticipate merge window to start Jan 7th
   * Initial plan - 1 week starting Sat, Dec 23rd to Tue, Jan 2nd
   * Polling in the meeting: 5 votes for 1 week of shutdown, 2 votes for 2 weeks
   * net-next will be closed for new features (fixes for code in
     net-next will be accepted)

 * Dealing with inter-dependencies w/ other trees: what if something
   that landed in net-next is needed in RDMA? If it’s already in, it’s
   too late, if we’re told in advance we can make a “stable branch”.
   Andrew: note that only build time dependencies are a requirement, if
   the functionality doesn’t work in either tree until the merge window
   - that’s fine. 

 * Next meeting on January 2nd (skipping one!)

      parent reply	other threads:[~2023-12-05 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 18:07 [ANN] netdev call - Dec 4th Jakub Kicinski
2023-12-04 18:11 ` Jakub Kicinski
2023-12-05 18:16 ` Jakub Kicinski [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=20231205101649.4403be0d@kernel.org \
    --to=kuba@kernel.org \
    --cc=jiri@resnulli.us \
    --cc=netdev-driver-reviewers@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rrameshbabu@nvidia.com \
    /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;
as well as URLs for NNTP newsgroup(s).