From: Steven Rostedt <rostedt@goodmis.org>
To: Mark Brown <broonie@kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
tech-board-discuss@lists.linuxfoundation.org,
Chris Mason <clm@fb.clm>, Tibor Raschko <tibrasch@gmail.com>
Subject: Re: [Ksummit-discuss] [Tech-board-discuss] [PATCH] CodingStyle: Inclusive Terminology
Date: Thu, 9 Jul 2020 12:35:16 -0400 [thread overview]
Message-ID: <20200709123516.3972dee8@oasis.local.home> (raw)
In-Reply-To: <20200709161351.GF4960@sirena.org.uk>
On Thu, 9 Jul 2020 17:13:51 +0100
Mark Brown <broonie@kernel.org> wrote:
> On Thu, Jul 09, 2020 at 10:01:18AM -0600, Shuah Khan wrote:
> > On 7/9/20 4:43 AM, Mauro Carvalho Chehab wrote:
>
> > > For coherency, if "blacklist/whitelist" won't be used anymore, an
> > > alternative to graylist should also be provided.
>
> > What is "graylist"? Does it mean in between allow/deny?
>
> Yes. Typically it's used in situations where you don't want to deny
> something but might for example want to do extra checks to verify that
> things are OK.
The only time I use greylist is for postgrey, that when an email comes
in, it will initially reject it, expecting the mail server to try
again, and the second time it lets it through. This does stop a lot of
spam, at the cost of waiting up to a few hours for email :-/
-- Steve
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2020-07-09 16:35 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 20:02 [Ksummit-discuss] [PATCH] CodingStyle: Inclusive Terminology Dan Williams
2020-07-04 20:31 ` Randy Dunlap
2020-07-04 23:41 ` Dave Airlie
2020-07-05 0:10 ` Matthew Wilcox
2020-07-05 1:10 ` [Ksummit-discuss] [Tech-board-discuss] " Kees Cook
2020-07-05 2:44 ` Randy Dunlap
2020-07-06 11:15 ` Michael Kerrisk (man-pages)
2020-07-06 15:53 ` Kees Cook
2020-07-05 2:54 ` [Ksummit-discuss] " Dave Airlie
2020-07-04 20:44 ` Stephen Rothwell
2020-07-04 23:34 ` Dave Airlie
2020-07-05 2:12 ` Stephen Rothwell
2020-07-05 2:56 ` Dave Airlie
2020-07-05 3:23 ` James Bottomley
2020-07-05 3:26 ` Stephen Rothwell
2020-07-04 21:14 ` Olof Johansson
2020-07-04 21:25 ` [Ksummit-discuss] [Tech-board-discuss] " James Bottomley
2020-07-04 21:51 ` Joe Perches
2020-07-04 23:39 ` Dave Airlie
2020-07-05 0:08 ` Joe Perches
2020-07-05 1:32 ` Kees Cook
2020-07-05 17:50 ` opal hart
2020-07-04 23:42 ` [Ksummit-discuss] " Dave Airlie
2020-07-05 0:12 ` Matthew Wilcox
2020-07-06 7:06 ` NeilBrown
2020-07-06 7:10 ` NeilBrown
2020-07-06 7:22 ` Greg Kroah-Hartman
2020-07-06 7:53 ` Geert Uytterhoeven
2020-07-06 10:22 ` Greg Kroah-Hartman
2020-07-06 12:51 ` Matthew Wilcox
2020-07-06 12:59 ` Joe Perches
2020-07-06 13:04 ` Matthew Wilcox
2020-07-06 13:30 ` Joe Perches
2020-07-09 11:11 ` Mauro Carvalho Chehab
2020-07-13 4:25 ` Vinod Koul
2020-07-13 15:55 ` Dan Williams
2020-07-05 0:41 ` Kees Cook
2020-07-07 4:30 ` Dan Williams
2020-07-10 16:52 ` Andy Lutomirski
2020-07-05 4:55 ` Willy Tarreau
2020-07-06 3:13 ` Daniel Palmer
2020-07-06 12:45 ` Chris Mason via Ksummit-discuss
2020-07-06 14:06 ` Laurent Pinchart
2020-07-06 15:55 ` Chris Mason via Ksummit-discuss
2020-07-06 16:06 ` Mike Rapoport
2020-07-07 4:17 ` Dan Williams
2020-07-06 15:22 ` Arvind Sankar
2020-07-06 15:40 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
2020-07-06 13:23 ` [Ksummit-discuss] " Tibor Raschko
2020-07-06 16:29 ` Andy Lutomirski
2020-07-07 4:00 ` Dan Williams
2020-07-07 5:56 ` Kees Cook
2020-07-07 6:49 ` Mike Rapoport
2020-07-07 13:37 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
2020-07-07 15:24 ` Bird, Tim
2020-07-07 15:33 ` Randy Dunlap
2020-07-07 15:41 ` Steven Rostedt
2020-07-07 15:55 ` Bird, Tim
2020-07-07 6:56 ` [Ksummit-discuss] " Harrosh, Boaz
2020-07-07 8:54 ` Kees Cook
2020-07-07 13:41 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
2020-07-07 14:45 ` Mike Rapoport
2020-07-07 20:56 ` Kees Cook
2020-07-07 21:48 ` [Ksummit-discuss] " Arvind Sankar
2020-07-07 12:13 ` Mark Brown
2020-07-06 18:30 ` [Ksummit-discuss] [Tech-board-discuss] " Shuah Khan
2020-07-06 23:58 ` Tibor Raschko
[not found] ` <20200709124327.369781a0@coco.lan>
2020-07-09 16:01 ` Shuah Khan
2020-07-09 16:13 ` Mark Brown
2020-07-09 16:32 ` James Bottomley
2020-07-09 16:35 ` Steven Rostedt [this message]
2020-07-07 4:04 ` Dan Williams
2020-07-06 19:15 ` Mark Brown
2020-07-07 0:48 ` Tibor Raschko
2020-07-07 21:26 ` Arvind Sankar
2020-07-07 23:54 ` Tibor Raschko
2020-07-07 4:08 ` Dan Williams
2020-07-07 9:36 ` Mark Brown
2020-07-06 21:31 ` [Ksummit-discuss] " Pavel Begunkov
2020-07-06 22:10 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
2020-07-06 22:17 ` Pavel Begunkov
2020-07-06 22:28 ` Steven Rostedt
2020-07-06 23:03 ` Pavel Begunkov
2020-07-08 3:42 ` Stephen Hemminger
2020-07-07 6:56 ` [Ksummit-discuss] " SeongJae Park via Ksummit-discuss
2020-07-08 7:12 ` Dan Williams
2020-07-08 9:28 ` SeongJae Park via Ksummit-discuss
2020-07-07 7:51 ` Christian Brauner
2020-07-17 8:35 ` Pavel Machek
2020-07-26 15:30 ` Laurent Pinchart
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=20200709123516.3972dee8@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=broonie@kernel.org \
--cc=clm@fb.clm \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=tech-board-discuss@lists.linuxfoundation.org \
--cc=tibrasch@gmail.com \
/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).