From: sashiko-bot@kernel.org
To: "Andrew Halaney" <andrew@amutable.com>
Cc: fsverity@lists.linux.dev, bpf@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 3/3] Documentation: keys: document IDs added since KEY_SPEC_REQKEY_AUTH_KEY
Date: Thu, 08 Oct 2026 21:01:58 +0000 [thread overview]
Message-ID: <sashiko-outbox-164582@kernel.org> (raw)
In-Reply-To: <20261008-ajhalaney-dmverity-key-identifier-v2-3-008456d189cb@amutable.com>
> The table of special key IDs stops at KEY_SPEC_REQKEY_AUTH_KEY.
> Fill in all the new ones.
>
> Suggested-by: Christian Brauner (Amutable) <brauner@kernel.org>
> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> Reviewed-by: Christian Brauner (Amutable) <brauner@kernel.org>
> Signed-off-by: Andrew Halaney <andrew@amutable.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261008-ajhalaney-dmverity-key-identifier-v2-0-008456d189cb@amutable.com?part=3
next prev parent reply other threads:[~2026-10-08 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 20:57 [PATCH bpf-next v2 0/3] keys: Add well known IDs for fs-verity/dm-verity keys Andrew Halaney
2026-10-08 20:57 ` [PATCH bpf-next v2 1/3] keys: add KEY_SPEC_DM_VERITY_KEYRING Andrew Halaney
2026-10-08 21:04 ` sashiko-bot
2026-10-08 21:44 ` bot+bpf-ci
2026-10-08 21:57 ` Andrew Halaney
2026-10-11 9:35 ` Manuel Huber
2026-10-12 13:12 ` Christian Brauner
2026-10-12 17:14 ` Manuel Huber
2026-10-08 20:57 ` [PATCH bpf-next v2 2/3] keys: add KEY_SPEC_FS_VERITY_KEYRING Andrew Halaney
2026-10-08 21:05 ` sashiko-bot
2026-10-08 20:57 ` [PATCH bpf-next v2 3/3] Documentation: keys: document IDs added since KEY_SPEC_REQKEY_AUTH_KEY Andrew Halaney
2026-10-08 21:01 ` sashiko-bot [this message]
2026-10-12 10:38 ` [PATCH bpf-next v2 0/3] keys: Add well known IDs for fs-verity/dm-verity keys Christian Brauner
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=sashiko-outbox-164582@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=andrew@amutable.com \
--cc=bpf@vger.kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-security-module@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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