From: Tyler Hicks <tyhicks@canonical.com>
To: Colin King <colin.king@canonical.com>, ecryptfs@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ecryptfs: fix spelling mistake: "cadidate" -> "candidate"
Date: Wed, 28 Mar 2018 20:46:13 -0500 [thread overview]
Message-ID: <ad0e32a8-e07d-4e9d-8042-b3920b4a40c7@canonical.com> (raw)
In-Reply-To: <20180302090708.25729-1-colin.king@canonical.com>
[-- Attachment #1.1: Type: text/plain, Size: 982 bytes --]
On 03/02/2018 03:07 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in debug message text.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Looks good to me. Thanks!
Tyler
> ---
> fs/ecryptfs/keystore.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ecryptfs/keystore.c b/fs/ecryptfs/keystore.c
> index c89a58cfc991..e74fe84d0886 100644
> --- a/fs/ecryptfs/keystore.c
> +++ b/fs/ecryptfs/keystore.c
> @@ -1880,7 +1880,7 @@ int ecryptfs_parse_packet_set(struct ecryptfs_crypt_stat *crypt_stat,
> candidate_auth_tok = &auth_tok_list_item->auth_tok;
> if (unlikely(ecryptfs_verbosity > 0)) {
> ecryptfs_printk(KERN_DEBUG,
> - "Considering cadidate auth tok:\n");
> + "Considering candidate auth tok:\n");
> ecryptfs_dump_auth_tok(candidate_auth_tok);
> }
> rc = ecryptfs_get_auth_tok_sig(&candidate_auth_tok_sig,
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-29 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 9:07 [PATCH] ecryptfs: fix spelling mistake: "cadidate" -> "candidate" Colin King
2018-03-29 1:46 ` Tyler Hicks [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-24 22:10 Colin King
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=ad0e32a8-e07d-4e9d-8042-b3920b4a40c7@canonical.com \
--to=tyhicks@canonical.com \
--cc=colin.king@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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 read-only IMAP folder(s) and NNTP newsgroup(s).