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: Re: -next status as at v7.1-rc4
Date: Mon, 18 May 2026 18:03:22 +0100 [thread overview]
Message-ID: <4d59bf02-2587-4d77-b555-7e6af39f1b6c@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
Hi Linus,
Things are a little rough right now, the week of no -next and some
coverage differences haven't helped - it's a good job Thierry was able
to cover for the first two weeks I was away.
Trees being held at old versions:
mm-nonmm-unstable next-20260424 (KUnit breakage on arm64, only
seen today probably only seen
now due to me running on
hardware not emulation)
We also have a nasty build failure in the vfs-brauner tree due to it
containing two semantically conflicting openat() flag additions
triggering a compile time assert, were it not for conflicts with other
vfs stuff which are addressed in the current merge I'd be holding that
at an old version too. As it is there are issues with my fixup so I'll
probably take another run at merging an old version tomorrow.
Trees with commits reverted for the final merge:
mm-hotfixes
origin
Trees with signoff problems:
bitmap (missing committer)
fs-next (missing author)
rdma (missing committer)
vfs-brauner (missing author)
Non-merge commits relative to Linus' tree: 5467
6387 files changed, 358135 insertions(+), 121907 deletions(-)
Top trees adding commits to -next:
1009 drm
391 net-next
249 mm-unstable
173 iio
172 v4l-dvb
Thaks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2026-05-18 17:03 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=4d59bf02-2587-4d77-b555-7e6af39f1b6c@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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