From: Jessica Yu <jeyu@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] modules: linux/moduleparam.h: drop duplicated word in a comment
Date: Mon, 20 Jul 2020 10:55:29 +0200 [thread overview]
Message-ID: <20200720085529.GA25857@linux-8ccs> (raw)
In-Reply-To: <e6006b9e-48dd-5b79-b676-eab2fc71c718@infradead.org>
+++ Randy Dunlap [17/07/20 16:36 -0700]:
>From: Randy Dunlap <rdunlap@infradead.org>
>
>Drop the doubled word "the" in a comment.
>
>Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>Cc: Jessica Yu <jeyu@kernel.org>
>---
> include/linux/moduleparam.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>--- linux-next-20200714.orig/include/linux/moduleparam.h
>+++ linux-next-20200714/include/linux/moduleparam.h
>@@ -108,7 +108,7 @@ struct kparam_array
> * ".") the kernel commandline parameter. Note that - is changed to _, so
> * the user can use "foo-bar=1" even for variable "foo_bar".
> *
>- * @perm is 0 if the the variable is not to appear in sysfs, or 0444
>+ * @perm is 0 if the variable is not to appear in sysfs, or 0444
> * for world-readable, 0644 for root-writable, etc. Note that if it
> * is writable, you may need to use kernel_param_lock() around
> * accesses (esp. charp, which can be kfreed when it changes).
Applied, thanks!
Jessica
prev parent reply other threads:[~2020-07-20 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 23:36 [PATCH] modules: linux/moduleparam.h: drop duplicated word in a comment Randy Dunlap
2020-07-20 8:55 ` Jessica Yu [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=20200720085529.GA25857@linux-8ccs \
--to=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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