From: Kees Cook <keescook@chromium.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Eric Biederman <ebiederm@xmission.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] binfmt_elf: fix comment typo s/reset/regset/
Date: Fri, 23 Jun 2023 09:38:46 -0700 [thread overview]
Message-ID: <202306230938.64FD809@keescook> (raw)
In-Reply-To: <0b2967c4a4141875c493e835d5a6f8f2d19ae2d6.1687499804.git.baruch@tkos.co.il>
On Fri, Jun 23, 2023 at 08:56:44AM +0300, Baruch Siach wrote:
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
>
> Resending with LKML in Cc. kvack.org MX does not like our mail server.
> ---
> fs/binfmt_elf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git fs/binfmt_elf.c fs/binfmt_elf.c
> index 8a884e795f6a..f304a3434c5a 100644
> --- fs/binfmt_elf.c
> +++ fs/binfmt_elf.c
Same formatting issue with this one.
> @@ -1773,7 +1773,7 @@ static int fill_thread_core_info(struct elf_thread_core_info *t,
> /*
> * NT_PRSTATUS is the one special case, because the regset data
> * goes into the pr_reg field inside the note contents, rather
> - * than being the whole note contents. We fill the reset in here.
> + * than being the whole note contents. We fill the regset in here.
> * We assume that regset 0 is NT_PRSTATUS.
> */
> fill_prstatus(&t->prstatus.common, t->task, signr);
But thank you; I've applied both to the execve tree:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=for-next/execve
-Kees
--
Kees Cook
prev parent reply other threads:[~2023-06-23 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 5:56 [PATCH RESEND] binfmt_elf: fix comment typo s/reset/regset/ Baruch Siach
2023-06-23 16:38 ` 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=202306230938.64FD809@keescook \
--to=keescook@chromium.org \
--cc=baruch@tkos.co.il \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.