From: SeongJae Park <sjpark@amazon.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: SeongJae Park <sjpark@amazon.com>, <akpm@linux-foundation.org>,
<colin.king@canonical.com>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>, SeongJae Park <sjpark@amazon.de>
Subject: Re: Re: [PATCH v2] scripts/spelling: Recommend blocklist/allowlist instead of blacklist/whitelist
Date: Tue, 9 Jun 2020 15:05:38 +0200 [thread overview]
Message-ID: <20200609130538.3573-1-sjpark@amazon.com> (raw)
In-Reply-To: <20200609125607.GB827447@kroah.com> (raw)
On Tue, 9 Jun 2020 14:56:07 +0200 Greg KH <gregkh@linuxfoundation.org> wrote:
> On Tue, Jun 09, 2020 at 02:25:49PM +0200, SeongJae Park wrote:
> > From: SeongJae Park <sjpark@amazon.de>
> >
> > This commit recommends the patches to replace 'blacklist' and
> > 'whitelist' with the 'blocklist' and 'allowlist', because the new
> > suggestions are incontrovertible, doesn't make people hurt, and more
> > self-explanatory.
> >
> > Signed-off-by: SeongJae Park <sjpark@amazon.de>
> > ---
> > scripts/spelling.txt | 2 ++
> > 1 file changed, 2 insertions(+)
>
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read:
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
Sorry, I only mistakenly Cc-ed stable@vger.kernel.org. Please don't pull this
in the stable tree.
Thanks,
SeongJae Park
>
> </formletter>
>
next prev parent reply other threads:[~2020-06-09 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 12:25 SeongJae Park
2020-06-09 12:56 ` Greg KH
2020-06-09 13:05 ` SeongJae Park [this message]
2020-06-10 1:35 ` Joe Perches
2020-06-10 5:33 ` SeongJae Park
2020-06-10 8:50 ` Jiri Slaby
2020-06-10 9:16 ` SeongJae Park
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=20200609130538.3573-1-sjpark@amazon.com \
--to=sjpark@amazon.com \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjpark@amazon.de \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®