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: <CAJZ5v0hAYpBWTpfJV6ZVX0tLiZZ-S5ABxpmqckxYcPyMyZrJfA@mail.gmail.com>
Date: Thu, 18 Sep 2025 23:22:57 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: "lihuisong (C)" <lihuisong@...wei.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>, lenb@...nel.org, linux-acpi@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linuxarm@...wei.com, 
	jonathan.cameron@...wei.com, zhanjie9@...ilicon.com, zhenglifeng1@...wei.com, 
	yubowen8@...wei.com
Subject: Re: [PATCH v3 3/3] ACPI: processor: Do not expose the global
 acpi_idle_driver variable

On Thu, Sep 18, 2025 at 2:23 PM lihuisong (C) <lihuisong@...wei.com> wrote:
>
>
> 在 2025/9/18 4:01, Rafael J. Wysocki 写道:
> > On Thu, Sep 11, 2025 at 1:24 PM Huisong Li <lihuisong@...wei.com> wrote:
> >> Currently, processor_driver just use the global acpi_idle_driver variable
> >> to check if the cpuidle driver is acpi_idle_driver. Actually, there is no
> >> need to expose this global variable defined in processor_idle.c to outside.
> >> So move the related logical to acpi_processor_power_init() and do not
> >> expose it.
> > And it can also be made static, can't it?
> ok, will do it in next version. Thanks.

You may as well rebase it on top of this one:

https://lore.kernel.org/linux-acpi/5044465.31r3eYUQgx@rafael.j.wysocki/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ