| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 3 May 2021 09:20:45 -0700
From: Matthias Kaehlcke <mka@...omium.org>
To: Sibi Sankar <sibis@...eaurora.org>
Cc: bjorn.andersson@...aro.org, viresh.kumar@...aro.org,
swboyd@...omium.org, agross@...nel.org, robh+dt@...nel.org,
rjw@...ysocki.net, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, dianders@...omium.org
Subject: Re: [PATCH 1/2] cpufreq: blacklist SC7280 in cpufreq-dt-platdev
On Fri, Apr 30, 2021 at 07:58:20PM +0530, Sibi Sankar wrote:
> Subject: cpufreq: blacklist SC7280 in cpufreq-dt-platdev
>
> Add SC7280 to cpufreq-dt-platdev blacklist since the actual scaling is
> handled by the 'qcom-cpufreq-hw' driver.
The coding style recommends the use of "allowlist" or "passlist" of
"blacklist":
https://elixir.bootlin.com/linux/v5.12/source/Documentation/process/coding-style.rst#L338
It's existing code so you aren't necessarily expected to change it. But
you could still use the recommended terminology in the commit message.
Powered by blists - more mailing lists