From: Thierry Reding <thierry.reding@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: -next status at v7.1-rc1
Date: Mon, 27 Apr 2026 16:52:06 +0200 [thread overview]
Message-ID: <ae91tYSmPir2cFaG@orome> (raw)
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
Hi Linus,
Mark predicted that linux-next was going to be relatively easy right
after v7.1-rc1. Not too much going on at the moment, just some fallout
from various changes in bpf-next that I reported (and were already
known, judging by the feedback I got) and that will hopefully get fixed
soon.
I got through the merge pretty quickly, but I'm still finding my way
around the scripts and had to rewrite some of them to match my build
infrastructure. The builds should roughly cover what Mark and Stephen
do. I'm sure various builders like KernelCI will complete the results.
Trees being held at old versions:
bpf-next next-20260424
No trees have signoff problems
Non-merge commits relative to Linus' tree: 775
998 files changed, 91327 insertions(+), 10126 deletions(-)
Top trees adding commits to -next:
98 amdgpu
96 drm-xe
54 mm-nonmm-unstable
40 stm32
38 sched-ext
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2026-04-27 14:52 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=ae91tYSmPir2cFaG@orome \
--to=thierry.reding@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=torvalds@linux-foundation.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