From: Eric Biggers <ebiggers@google.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
jaegeuk@kernel.org, tytso@mit.edu
Subject: Re: [PATCH 2/2] fscrypto: Fix fscrypt_decrypt_page() doc string
Date: Fri, 21 Oct 2016 13:02:49 -0700 [thread overview]
Message-ID: <20161021200249.GB137744@google.com> (raw)
In-Reply-To: <1476824089-6841-3-git-send-email-richard@nod.at>
On Tue, Oct 18, 2016 at 10:54:49PM +0200, Richard Weinberger wrote:
> Most likely a copy&paste error from the f2fs import.
>
> Signed-off-by: Richard Weinberger <richard@nod.at>
> ---
> fs/crypto/crypto.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/crypto/crypto.c b/fs/crypto/crypto.c
> index 1637a0450b9f..d789ddbc0a46 100644
> --- a/fs/crypto/crypto.c
> +++ b/fs/crypto/crypto.c
> @@ -265,7 +265,7 @@ struct page *fscrypt_encrypt_page(struct inode *inode,
> EXPORT_SYMBOL(fscrypt_encrypt_page);
>
> /**
> - * f2crypt_decrypt_page() - Decrypts a page in-place
> + * fscrypt_decrypt_page() - Decrypts a page in-place
> * @page: The page to decrypt. Must be locked.
> *
> * Decrypts page in-place using the ctx encryption context.
> --
> 2.7.3
>
Looks fine.
Reviewed-by: Eric Biggers <ebiggers@google.com>
prev parent reply other threads:[~2016-10-21 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 20:54 fscrypto: Two trivial patches Richard Weinberger
2016-10-18 20:54 ` [PATCH 1/2] fscrypto: Fix log string in do_crypto() Richard Weinberger
2016-10-21 20:02 ` Eric Biggers
2016-10-18 20:54 ` [PATCH 2/2] fscrypto: Fix fscrypt_decrypt_page() doc string Richard Weinberger
2016-10-21 20:02 ` 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=20161021200249.GB137744@google.com \
--to=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--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.