linux-kernel - Re: [PATCH v1] ACPI: Declare acpi_blacklisted() only if CONFIG

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]

Date: Sun, 28 Apr 2024 21:06:34 -0700
From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
 "Rafael J. Wysocki" <rafael@...nel.org>
Cc: "Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
 linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
 Len Brown <lenb@...nel.org>
Subject: Re: [PATCH v1] ACPI: Declare acpi_blacklisted() only if CONFIG_X86 is
 enabled

On 4/23/24 6:02 AM, Andy Shevchenko wrote:
> On Mon, Apr 22, 2024 at 06:37:59PM +0200, Rafael J. Wysocki wrote:
>> On Sun, Apr 7, 2024 at 8:33 AM Kuppuswamy Sathyanarayanan
>> <sathyanarayanan.kuppuswamy@...ux.intel.com> wrote:
> ...
>
>> Applied (as 6.10 material), but it looks to me like this declaration
>> could be moved away from this header file at all, as the function is
>> only used in one place in arch-x86 code.
> Yes, we probably may move it to asm/acpi.h for x86.
>
> I don't remember if I ever expressed that idea, but I definitely was thinking
> about this.
>

Makes sense. I have moved it to asm/acpi.h

https://lore.kernel.org/lkml/20240429040441.748479-1-sathyanarayanan.kuppuswamy@linux.intel.com/T/#u

-- 
Sathyanarayanan Kuppuswamy
Linux Kernel Developer