From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 0/3] fscrypt: misc cleanups
Date: Wed, 20 May 2020 15:51:56 -0700 [thread overview]
Message-ID: <20200520225156.GA19246@sol.localdomain> (raw)
In-Reply-To: <20200511191358.53096-1-ebiggers@kernel.org>
On Mon, May 11, 2020 at 12:13:55PM -0700, Eric Biggers wrote:
> In fs/crypto/ and fscrypt.h, fix all kerneldoc warnings, and fix some
> coding style inconsistencies in function declarations.
>
> Eric Biggers (3):
> fscrypt: fix all kerneldoc warnings
> fscrypt: name all function parameters
> fscrypt: remove unnecessary extern keywords
>
> fs/crypto/crypto.c | 9 +-
> fs/crypto/fname.c | 52 +++++++++---
> fs/crypto/fscrypt_private.h | 88 +++++++++----------
> fs/crypto/hooks.c | 4 +-
> fs/crypto/keysetup.c | 9 +-
> fs/crypto/policy.c | 19 ++++-
> include/linux/fscrypt.h | 165 ++++++++++++++++++------------------
> 7 files changed, 193 insertions(+), 153 deletions(-)
>
All applied to fscrypt.git#master for 5.8.
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2020-05-20 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 19:13 [f2fs-dev] [PATCH 0/3] fscrypt: misc cleanups Eric Biggers
2020-05-11 19:13 ` [f2fs-dev] [PATCH 1/3] fscrypt: fix all kerneldoc warnings Eric Biggers
2020-05-11 19:13 ` [f2fs-dev] [PATCH 2/3] fscrypt: name all function parameters Eric Biggers
2020-05-11 19:13 ` [f2fs-dev] [PATCH 3/3] fscrypt: remove unnecessary extern keywords Eric Biggers
2020-05-20 22:51 ` 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=20200520225156.GA19246@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).