From: Tyler Hicks <code@tyhicks.com>
To: Jules Maselbas <jmaselbas@kalray.eu>
Cc: linux-kernel@vger.kernel.org, ecryptfs@vger.kernel.org
Subject: Re: [PATCH] fs/ecryptfs: Fix repeated word in comments
Date: Sun, 25 Sep 2022 12:17:03 -0500 [thread overview]
Message-ID: <20220925171703.GC59018@sequoia> (raw)
In-Reply-To: <20220826100052.22945-9-jmaselbas@kalray.eu>
On 2022-08-26 12:00:37, Jules Maselbas wrote:
> Remove redundant word `the`.
>
> CC: ecryptfs@vger.kernel.org
> Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu>
> ---
Thanks for the patch but I applied this one that was sent a little
earlier:
https://lore.kernel.org/lkml/20220722100212.79490-1-slark_xiao@163.com/
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 3fe41964c0d8..2452d6fd7062 100644
> --- a/fs/ecryptfs/keystore.c
> +++ b/fs/ecryptfs/keystore.c
> @@ -878,7 +878,7 @@ struct ecryptfs_parse_tag_70_packet_silly_stack {
> * @filename: This function kmalloc's the memory for the filename
> * @filename_size: This function sets this to the amount of memory
> * kmalloc'd for the filename
> - * @packet_size: This function sets this to the the number of octets
> + * @packet_size: This function sets this to the number of octets
> * in the packet parsed
> * @mount_crypt_stat: The mount-wide cryptographic context
> * @data: The memory location containing the start of the tag 70
> --
> 2.17.1
>
prev parent reply other threads:[~2022-09-25 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 10:00 [PATCH] fs/ecryptfs: Fix repeated word in comments Jules Maselbas
2022-09-25 17:17 ` Tyler Hicks [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=20220925171703.GC59018@sequoia \
--to=code@tyhicks.com \
--cc=ecryptfs@vger.kernel.org \
--cc=jmaselbas@kalray.eu \
--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 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.