From: Luca Boccassi <Luca.Boccassi@microsoft.com>
To: "ebiggers@kernel.org" <ebiggers@kernel.org>,
"linux-fscrypt@vger.kernel.org" <linux-fscrypt@vger.kernel.org>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"victorhsieh@google.com" <victorhsieh@google.com>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
"Jes.Sorensen@gmail.com" <Jes.Sorensen@gmail.com>,
"maco@android.com" <maco@android.com>,
"paullawrence@google.com" <paullawrence@google.com>
Subject: Re: [PATCH 1/4] fs-verity: remove filenames from file comments
Date: Mon, 16 Nov 2020 11:21:25 +0000 [thread overview]
Message-ID: <b305fda4e0fc0ec57b318629d2f5c9760e5aa259.camel@microsoft.com> (raw)
In-Reply-To: <20201113211918.71883-2-ebiggers@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
On Fri, 2020-11-13 at 13:19 -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Embedding the file path inside kernel source code files isn't
> particularly useful as often files are moved around and the paths become
> incorrect. checkpatch.pl warns about this since v5.10-rc1.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> fs/verity/enable.c | 2 +-
> fs/verity/hash_algs.c | 2 +-
> fs/verity/init.c | 2 +-
> fs/verity/measure.c | 2 +-
> fs/verity/open.c | 2 +-
> fs/verity/signature.c | 2 +-
> fs/verity/verify.c | 2 +-
> 7 files changed, 7 insertions(+), 7 deletions(-)
Acked-by: Luca Boccassi <luca.boccassi@microsoft.com>
--
Kind regards,
Luca Boccassi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-16 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 21:19 [PATCH 0/4] fs-verity cleanups Eric Biggers
2020-11-13 21:19 ` [PATCH 1/4] fs-verity: remove filenames from file comments Eric Biggers
2020-11-16 11:21 ` Luca Boccassi [this message]
2020-11-13 21:19 ` [PATCH 2/4] fs-verity: rename fsverity_signed_digest to fsverity_formatted_digest Eric Biggers
2020-11-13 21:19 ` [PATCH 3/4] fs-verity: rename "file measurement" to "file digest" Eric Biggers
2020-11-16 11:21 ` Luca Boccassi
2020-11-13 21:19 ` [PATCH 4/4] fs-verity: move structs needed for file signing to UAPI header Eric Biggers
2020-11-16 11:25 ` Luca Boccassi
2020-11-16 19:57 ` [PATCH 0/4] fs-verity cleanups 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=b305fda4e0fc0ec57b318629d2f5c9760e5aa259.camel@microsoft.com \
--to=luca.boccassi@microsoft.com \
--cc=Jes.Sorensen@gmail.com \
--cc=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=maco@android.com \
--cc=paullawrence@google.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