Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   "Bird, Tim" <Tim.Bird@sony.com>
To:     Steven Rostedt <rostedt@goodmis.org>,
        Mike Rapoport <rppt@linux.ibm.com>
CC:     ksummit <ksummit-discuss@lists.linuxfoundation.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        LKML <linux-kernel@vger.kernel.org>,
        "tech-board-discuss@lists.linuxfoundation.org" 
        <tech-board-discuss@lists.linuxfoundation.org>,
        Chris Mason <clm@fb.clm>
Subject: RE: [Ksummit-discuss] [Tech-board-discuss] [PATCH] CodingStyle:
 Inclusive Terminology
Thread-Topic: [Ksummit-discuss] [Tech-board-discuss] [PATCH] CodingStyle:
 Inclusive Terminology
Thread-Index: AQHWVGPIwQycxLw5iEauvXmlP6ObnKj8O1Fw
Date:   Tue, 7 Jul 2020 15:24:28 +0000
Message-ID: <CY4PR13MB117519F548B125CB2F10F50FFD660@CY4PR13MB1175.namprd13.prod.outlook.com>
References: <159389297140.2210796.13590142254668787525.stgit@dwillia2-desk3.amr.corp.intel.com>
 <CALCETrXewAK4_fpaJNDHJVDK9mUcjghA5HwYvZFQNYVfC9M+OQ@mail.gmail.com>
 <202007062234.A90F922DF@keescook> <20200707064921.GA9411@linux.ibm.com>
 <20200707093727.22aa39e2@oasis.local.home>
In-Reply-To: <20200707093727.22aa39e2@oasis.local.home>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5ce181e0-2d3b-41f4-4b80-08d82289d723
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jul 2020 15:24:28.6604
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 66c65d8a-9158-4521-a2d8-664963db48e4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Et63W4+weARoAQv13XH0oqTO+nzrsM6CLWN9uDw1SJiORm/ihVpV1jTvC3+giZnK1fS8KiI7lGs1+TSoAvBXDQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR1301MB2104
X-Sony-Outbound-GUID: aNzJF2sxxi3l0y-sxPLvNqdO2Gpz9q1-
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235,18.0.687
 definitions=2020-07-07_08:2020-07-07,2020-07-07 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 phishscore=0
 cotscore=-2147483648 adultscore=0 mlxlogscore=999 suspectscore=0
 priorityscore=1501 mlxscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0
 impostorscore=0 bulkscore=0 malwarescore=0 classifier=spam adjust=0
 reason=mlx scancount=1 engine=8.12.0-2004280000
 definitions=main-2007070113
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


> -----Original Message-----
> From: Steven Rostedt
>=20
> On Tue, 7 Jul 2020 09:49:21 +0300
> Mike Rapoport <rppt@linux.ibm.com> wrote:
>=20
> > > But that's all fine. The change is easy to do and is more descriptive
> > > even if I can't find terms that don't collide with my internal gramma=
r
> > > checker. ;)
> >
> > How about yeslist and nolist? ;-)
>=20
> I was thinking good-list / bad-list.
>=20
> /me that has been doing a lot of git bisect lately...

I think it depends on the context.  I'd prefer a grammatically awkward verb=
 that described
the action more specifically, than a grammatically nicer generic term.  In =
other words,
yes/no, good/bad don't mean that much to me, unless it's obvious from conte=
xt
what the effect will be.  With something like allow/deny, I have a pretty c=
lear mental
model of what the code is going to do.

 -- Tim