linux-kernel - Re: [PATCH 1/2] units: Add the HZ_PER

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-next>] [day] [month] [year] [list]

Message-Id: <20210303163125.dcc0a086a939a58ed30750e8@linux-foundation.org>
Date:   Wed, 3 Mar 2021 16:31:25 -0800
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Andy Shevchenko <andy.shevchenko@...il.com>
Cc:     Daniel Lezcano <daniel.lezcano@...aro.org>,
        "rafael@...nel.org" <rafael@...nel.org>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Lukasz Luba <lukasz.luba@....com>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] units: Add the HZ_PER_KHZ macro

On Wed, 24 Feb 2021 10:39:36 +0200 Andy Shevchenko <andy.shevchenko@...il.com> wrote:

> On Wednesday, February 24, 2021, Andy Shevchenko <andy.shevchenko@...il.com>
> wrote:
> 
> >
> >
> > On Tuesday, February 23, 2021, Daniel Lezcano <daniel.lezcano@...aro.org>
> > wrote:
> >
> >> The macro for the unit conversion for frequency is duplicated in
> >> different places.
> >>
> >> Provide this macro in the 'units' header, so it can be reused.
> >>
> >>
> >
> > Thanks! That was the idea behind my reviews to add those definitions
> > explicitly in the users. I just want to be sure you covered them all. Also
> > there are few non-standard names for above in some drivers (they can be
> > fixed on per driver basis in separate patches though).
> >
> >
> 
> Seems you introduced a common macro and forget about dropping it elsewhere.
> 
> https://elixir.bootlin.com/linux/latest/A/ident/HZ_PER_MHZ

Yes.  And HZ_PER_KHZ.

Also, why make them signed types?  Negative Hz is physically
nonsensical.  If that upsets some code somewhere because it was dealing
with signed types then, well, that code needed fixing anyway.

Ditto MILLIWATT_PER_WATT and friends, sigh.