From: Eric Biggers <ebiggers@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: aalbersh@kernel.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] fsverity: Explicitly require FMODE_READ to retrieve hashes" failed to apply to 6.18-stable tree
Date: Sat, 7 Nov 2026 13:26:33 -0800 [thread overview]
Message-ID: <20261107212633.GA137269@quark> (raw)
In-Reply-To: <au-Ux9Sunxhat_jo@laps>
On Sat, Nov 07, 2026 at 04:14:47PM -0500, Sasha Levin wrote:
> So I feel we have had the Cc discussion quite a few times now. We really have
> to limit how many mails end up going out: this last release had thousands of
> mails which took hours to send. Adding more lists will simply kill the mail
> server and will harm everyone.
>
> We have solutions for that!
>
> See Konstantin's writeup[1] about lei with filters like dfn: or dfhh:.
>
> We're not going to change this on our end: the kernel.org folks will complain,
> mails will take days, and people will be grumpy at us.
>
> If this is really not something you can work around, then we can figure out a
> filter to exclude your patches so that all of us can continue being happy going
> forward.
>
>
> [1] https://people.kernel.org/monsieuricon/lore-lei-part-1-getting-started
I've already started to use lei to work around this issue with the
stable process, but everyone else will as well, which seems unlikely to
work well. This also effectively means that subsystem mailing lists are
deprecated, as some of the development process is happening off-list.
- Eric
next prev parent reply other threads:[~2026-11-07 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 10:15 FAILED: patch "[PATCH] fsverity: Explicitly require FMODE_READ to retrieve hashes" failed to apply to 6.18-stable tree Sasha Levin
2026-11-07 19:04 ` Eric Biggers
2026-11-07 21:14 ` Sasha Levin
2026-11-07 21:26 ` Eric Biggers [this message]
2026-11-08 13:47 ` Greg KH
2026-11-08 20:36 ` Eric Biggers
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=20261107212633.GA137269@quark \
--to=ebiggers@kernel.org \
--cc=aalbersh@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox