linux-kernel - Re: [PATCH v2 00/13] Rid W=1 warnings in CPUFreq

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJZ5v0jra1Q=L9H-9jJTFERbwSt5t4iF=vmtv9_01roa6bPB3A@mail.gmail.com>
Date:   Wed, 15 Jul 2020 15:23:56 +0200
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Lee Jones <lee.jones@...aro.org>
Cc:     "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Viresh Kumar <viresh.kumar@...aro.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux PM <linux-pm@...r.kernel.org>
Subject: Re: [PATCH v2 00/13] Rid W=1 warnings in CPUFreq

On Wed, Jul 15, 2020 at 10:27 AM Lee Jones <lee.jones@...aro.org> wrote:
>
> This set is part of a larger effort attempting to clean-up W=1
> kernel builds, which are currently overwhelmingly riddled with
> niggly little warnings.
>
> After these patches are applied, the build system no longer
> complains about any W=0 nor W=1 level warnings in drivers/cpufreq.
>
> Hurrah!
>
> Changelog
>
> v1 => v2:
>  - Collect *-bys
>  - Use __maybe_unused instead of removing device IDs
>  - Use __always_unused instead of using unused variables
>  - Include architecture header instead of creating new include file
>
> Lee Jones (13):
>   cpufreq: freq_table: Demote obvious misuse of kerneldoc to standard
>     comment blocks
>   cpufreq: cpufreq: Demote lots of function headers unworthy of
>     kerneldoc status
>   cpufreq: cpufreq_governor: Demote store_sampling_rate() header to
>     standard comment block
>   cpufreq: sti-cpufreq: Fix some formatting and misspelling issues
>   cpufreq: pasemi: Include header file for {check,restore}_astate
>     prototypes
>   cpufreq: powernv-cpufreq: Functions only used in call-backs should be
>     static
>   cpufreq: powernv-cpufreq: Fix a bunch of kerneldoc related issues
>   cpufreq: acpi-cpufreq: Mark 'dummy' variable as __always_unused
>   cpufreq: acpi-cpufreq: Mark sometimes used ID structs as
>     __maybe_unused
>   cpufreq: powernow-k8: Mark 'hi' and 'lo' dummy variables as
>     __always_unused
>   cpufreq: pcc-cpufreq: Mark sometimes used ID structs as __maybe_unused
>   cpufreq: intel_pstate: Supply struct attribute description for
>     get_aperf_mperf_shift()
>   cpufreq: amd_freq_sensitivity: Mark sometimes used ID structs as
>     __maybe_unused
>
>  drivers/cpufreq/acpi-cpufreq.c         |  8 +++----
>  drivers/cpufreq/amd_freq_sensitivity.c |  2 +-
>  drivers/cpufreq/cpufreq.c              | 32 ++++++++++++++------------
>  drivers/cpufreq/cpufreq_governor.c     |  2 +-
>  drivers/cpufreq/freq_table.c           |  6 ++---
>  drivers/cpufreq/intel_pstate.c         |  2 ++
>  drivers/cpufreq/pasemi-cpufreq.c       |  2 ++
>  drivers/cpufreq/pcc-cpufreq.c          |  2 +-
>  drivers/cpufreq/powernow-k8.c          |  4 ++--
>  drivers/cpufreq/powernv-cpufreq.c      | 15 ++++++------
>  drivers/cpufreq/sti-cpufreq.c          |  8 +++----
>  11 files changed, 45 insertions(+), 38 deletions(-)
>
> --

All patches except for the [04/13] (applied by Viresh) and [06/13]
(requested to be ignored) applied as 5.9 material with the ACKs from
Viresh, thanks!