From: Kees Cook <keescook@chromium.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] sysctl: fix typos in comments
Date: Mon, 2 Jul 2018 11:41:18 -0700 [thread overview]
Message-ID: <CAGXu5jL-GUwgL7XLJS6=9BFuidbCAcUpDKgJV8dq41zd3yvA7A@mail.gmail.com> (raw)
In-Reply-To: <bb09a8b9-f984-6dd4-b07b-3ecaf200862e@infradead.org>
On Sun, Jul 1, 2018 at 11:22 AM, Randy Dunlap <rdunlap@infradead.org> wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix a few typos/spellos in kernel/sysctl.c.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>
> Cc: Kees Cook <keescook@chromium.org>
Acked-by: Kees Cook <keescook@chromium.org>
-Kees
> ---
> kernel/sysctl.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> --- lnx-418-rc2.orig/kernel/sysctl.c
> +++ lnx-418-rc2/kernel/sysctl.c
> @@ -222,7 +222,7 @@ static int proc_dopipe_max_size(struct c
> void __user *buffer, size_t *lenp, loff_t *ppos);
>
> #ifdef CONFIG_MAGIC_SYSRQ
> -/* Note: sysrq code uses it's own private copy */
> +/* Note: sysrq code uses its own private copy */
> static int __sysrq_enabled = CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE;
>
> static int sysrq_sysctl_handler(struct ctl_table *table, int write,
> @@ -1973,13 +1973,13 @@ static void warn_sysctl_write(struct ctl
> }
>
> /**
> - * proc_first_pos_non_zero_ignore - check if firs position is allowed
> + * proc_first_pos_non_zero_ignore - check if first position is allowed
> * @ppos: file position
> * @table: the sysctl table
> *
> * Returns true if the first position is non-zero and the sysctl_writes_strict
> * mode indicates this is not allowed for numeric input types. String proc
> - * hadlers can ignore the return value.
> + * handlers can ignore the return value.
> */
> static bool proc_first_pos_non_zero_ignore(loff_t *ppos,
> struct ctl_table *table)
>
--
Kees Cook
Pixel Security
prev parent reply other threads:[~2018-07-02 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 18:22 [PATCH] sysctl: fix typos in comments Randy Dunlap
2018-07-02 18:41 ` Kees Cook [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='CAGXu5jL-GUwgL7XLJS6=9BFuidbCAcUpDKgJV8dq41zd3yvA7A@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@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;
as well as URLs for NNTP newsgroup(s).