linux-kernel - Re: [PATCH] cpufreq: sparc: Don't allocate 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] [day] [month] [year] [list]

Message-ID: <20230515091454.hhpkkyqvqtxcsoaa@vireshk-i7>
Date:   Mon, 15 May 2023 14:44:54 +0530
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     "Rafael J. Wysocki" <rafael@...nel.org>
Cc:     linux-pm@...r.kernel.org,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Markus Elfring <Markus.Elfring@....de>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cpufreq: sparc: Don't allocate cpufreq_driver dynamically

On 11-05-23, 12:21, Rafael J. Wysocki wrote:
> On Thu, May 11, 2023 at 11:01 AM Viresh Kumar <viresh.kumar@...aro.org> wrote:
> >
> > There is no point allocating the cpufreq driver dynamically and add so
> > much complexity in the driver.
> >
> > Do what is done for other cpufreq drivers and statically allocate the
> > cpufreq driver.
> >
> > Reported-by: Markus Elfring <Markus.Elfring@....de>
> > Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> 
> Acked-by: Rafael J. Wysocki <rafael@...nel.org>

Applied. Thanks.

-- 
viresh