From: Kees Cook <keescook@chromium.org>
To: ebiederm@xmission.com, Al Viro <viro@zeniv.linux.org.uk>,
jiaming@nfschina.com
Cc: Kees Cook <keescook@chromium.org>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
liqiong@nfschina.com, renyu@nfschina.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] exec: Fix a spelling mistake
Date: Fri, 1 Jul 2022 15:07:00 -0700 [thread overview]
Message-ID: <165671321774.2472190.15847040926491629125.b4-ty@chromium.org> (raw)
In-Reply-To: <20220629072932.27506-1-jiaming@nfschina.com>
On Wed, 29 Jun 2022 15:29:32 +0800, Zhang Jiaming wrote:
> Change 'wont't' to 'won't'.
Applied to for-next/execve, thanks!
[1/1] exec: Fix a spelling mistake
https://git.kernel.org/kees/c/5036793d7dbd
--
Kees Cook
prev parent reply other threads:[~2022-07-01 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 7:29 Zhang Jiaming
2022-06-30 0:47 ` Souptick Joarder
2022-07-01 22:07 ` 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=165671321774.2472190.15847040926491629125.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=ebiederm@xmission.com \
--cc=jiaming@nfschina.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liqiong@nfschina.com \
--cc=renyu@nfschina.com \
--cc=viro@zeniv.linux.org.uk \
/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