From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org
Subject: [ANN] net-next is CLOSED
Date: Mon, 24 Mar 2025 07:55:39 -0700 [thread overview]
Message-ID: <20250324075539.2b60eb42@kernel.org> (raw)
Hi!
Linus just cut final v6.14:
https://lore.kernel.org/all/CAHk-=wg7TO09Si5tTPyhdrLLvyYtVmCf+GGN4kVJ0=Xk=5TE3g@mail.gmail.com/
a day late, coincidentally, kicking off what we expect to also
be a fairly messy merge window for us. Multiple core maintainers
have taken time off in March, and we're sitting on a larger than
usual pile of unprocessed patches.
Our PR will likely not be ready for another couple of days,
so net-next will be "closed" for real -next material, but open
for fixes to already merged patches. IOW please don't post new
features / drivers any more, but continue to send fixes as
"PATCH net-next" where appropriate.
next reply other threads:[~2025-03-24 14:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 14:55 Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-12 21:22 [ANN] net-next is CLOSED Jakub Kicinski
2026-02-08 23:40 Jakub Kicinski
2025-12-01 1:45 Jakub Kicinski
2025-09-29 4:26 Jakub Kicinski
2025-07-25 0:44 Jakub Kicinski
2025-05-26 6:48 Paolo Abeni
2025-01-18 2:20 Jakub Kicinski
2024-12-21 2:28 Jakub Kicinski
2024-11-18 15:16 Jakub Kicinski
2024-09-13 1:12 Jakub Kicinski
2024-07-15 3:46 Jakub Kicinski
2024-05-13 13:51 Jakub Kicinski
2024-03-11 14:51 Jakub Kicinski
2024-01-08 1:22 Jakub Kicinski
2023-10-31 0:06 Jakub Kicinski
2023-08-28 0:23 [ANN] net-next is closed Jakub Kicinski
2023-08-28 8:17 ` Jiri Pirko
2023-06-26 2:30 Jakub Kicinski
2023-04-24 14:59 Jakub Kicinski
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=20250324075539.2b60eb42@kernel.org \
--to=kuba@kernel.org \
--cc=netdev-driver-reviewers@vger.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.