From: Konstantin Ryabitsev <mricon@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Luis Henriques <luis@igalia.com>,
linux-fscrypt@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Jarkko Sakkinen <jarkko@kernel.org>,
linux-fsdevel@vger.kernel.org, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+f55b043dacf43776b50c@syzkaller.appspotmail.com,
Mohammed EL Kadiri <med08elkadiri@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] fscrypt: Replace mk_users keyring with simple list
Date: Fri, 26 Jun 2026 23:20:42 -0400 [thread overview]
Message-ID: <20260626-capable-inventive-rhino-b9b8fa@lemur> (raw)
In-Reply-To: <20260626190232.GA1719948@google.com>
On Fri, Jun 26, 2026 at 07:02:32PM +0000, Eric Biggers wrote:
> It applies on top of
> "[PATCH] fscrypt: Fix key setup in edge case with multiple data unit sizes"
> (https://lore.kernel.org/linux-fscrypt/20260618180652.52742-1-ebiggers@kernel.org/).
> This time I tried just relying on the prerequisite-patch-id footer (as
> generated by 'git format-patch') to express the dependency. But
> evidently that still doesn't work: for one, 'b4 am' just ignores it.
FWIW, you have to use "b4 shazam" for it to apply the specified dependencies,
as "b4 am" just creates a mbox file and stuffing it full of deps is not really
the right approach.
HTH.
-K
prev parent reply other threads:[~2026-06-27 3:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 22:19 Eric Biggers
2026-06-26 8:16 ` Luis Henriques
2026-06-26 19:02 ` Eric Biggers
2026-06-26 20:29 ` Eric Biggers
2026-06-27 3:20 ` Konstantin Ryabitsev [this message]
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=20260626-capable-inventive-rhino-b9b8fa@lemur \
--to=mricon@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis@igalia.com \
--cc=med08elkadiri@gmail.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+f55b043dacf43776b50c@syzkaller.appspotmail.com \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®