From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: -next status as at v7.0-rc5
Date: Mon, 23 Mar 2026 18:08:40 +0000 [thread overview]
Message-ID: <cb2256d0-cfa9-424f-9dff-8704c3c8a1fa@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
Hi Linus,
Trees being held at old versions:
vfs-brauner next-20260312 (Fix applied today)
I'm also carrying a patch for ext4 fixing KUnit memory corruption that
manifests when we merge with the tip tree, the ext4 tree hasn't been
updated since January (before the fix was posted).
Trees with signoff problems:
hid (missing committer)
iommufd (missing committer)
qcom (missing author)
rdma-fixes (missing committer)
rdma (missing committer)
rpmsg (missing committer)
Non-merge commits relative to Linus' tree: 7417
7501 files changed, 482067 insertions(+), 147610 deletions(-)
Top trees adding commits to -next:
1073 drm
633 net-next
436 mm-unstable
272 tip
221 qcom
152 ksmbd
143 iio
139 sound-asoc
137 v4l-dvb
131 imx-mxs
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2026-03-23 18:08 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=cb2256d0-cfa9-424f-9dff-8704c3c8a1fa@sirena.org.uk \
--to=broonie@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