From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>,
Matthias Goergens <matthias.goergens@gmail.com>,
fsverity@lists.linux.dev
Subject: Re: [PATCH] MAINTAINERS: List the fsverity branches
Date: Thu, 24 Sep 2026 21:23:56 -0700 [thread overview]
Message-ID: <20260925042356.GA112369@sol> (raw)
In-Reply-To: <20260925041654.112935-1-ebiggers@kernel.org>
+Cc fsverity@lists.linux.dev
On Thu, Sep 24, 2026 at 09:16:54PM -0700, Eric Biggers wrote:
> The fsverity entry in MAINTAINERS has a T: entry but it doesn't mention
> which branches are used. Update it to have a T: entry for each branch.
>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
> MAINTAINERS | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c52ec2d7d3c1..2a4b4ef679cd 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -10706,7 +10706,8 @@ M: Theodore Y. Ts'o <tytso@mit.edu>
> L: fsverity@lists.linux.dev
> S: Supported
> Q: https://patchwork.kernel.org/project/fsverity/list/
> -T: git https://git.kernel.org/pub/scm/fs/fsverity/linux.git
> +T: git https://git.kernel.org/pub/scm/fs/fsverity/linux.git for-next
> +T: git https://git.kernel.org/pub/scm/fs/fsverity/linux.git for-current
> F: Documentation/filesystems/fsverity.rst
> F: fs/verity/
> F: include/linux/fsverity.h
>
> base-commit: 165768bb70265b5c38cf0b73fafd75be235f8b14
> --
> 2.55.0
>
next prev parent reply other threads:[~2026-09-25 4:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 4:16 [PATCH] MAINTAINERS: List the fsverity branches Eric Biggers
2026-09-25 4:23 ` Eric Biggers [this message]
2026-09-25 11:58 ` Matthias Goergens
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=20260925042356.GA112369@sol \
--to=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=matthias.goergens@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.