From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: Victor Hsieh <victorhsieh@google.com>,
Luca Boccassi <luca.boccassi@gmail.com>,
Jes Sorensen <Jes.Sorensen@gmail.com>
Subject: Re: [PATCH] fs-verity: rename fsverity_signed_digest to fsverity_formatted_digest
Date: Fri, 13 Nov 2020 13:21:41 -0800 [thread overview]
Message-ID: <X6745brG4qhs/OQn@sol.localdomain> (raw)
In-Reply-To: <X67TSUuGngILe8Kk@sol.localdomain>
On Fri, Nov 13, 2020 at 10:41:13AM -0800, Eric Biggers wrote:
> On Tue, Oct 27, 2020 at 12:11:06PM -0700, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > The name "struct fsverity_signed_digest" is causing confusion because it
> > isn't actually a signed digest, but rather it's the way that the digest
> > is formatted in order to be signed. Rename it to
> > "struct fsverity_formatted_digest" to prevent this confusion.
> >
> > Also update the struct's comment to clarify that it's specific to the
> > built-in signature verification support and isn't a requirement for all
> > fs-verity users.
> >
> > I'll be renaming this struct in fsverity-utils too.
> >
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
>
> Applied to fscrypt.git#fsverity for 5.11.
>
> - Eric
Actually, I decided to resend this as part of the series
https://lkml.kernel.org/linux-fscrypt/20201113211918.71883-1-ebiggers@kernel.org.
- Eric
prev parent reply other threads:[~2020-11-13 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 19:11 [PATCH] fs-verity: rename fsverity_signed_digest to fsverity_formatted_digest Eric Biggers
2020-10-27 21:17 ` Luca Boccassi
2020-11-13 18:41 ` Eric Biggers
2020-11-13 21:21 ` Eric Biggers [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=X6745brG4qhs/OQn@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=Jes.Sorensen@gmail.com \
--cc=linux-fscrypt@vger.kernel.org \
--cc=luca.boccassi@gmail.com \
--cc=victorhsieh@google.com \
/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