From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Zhang Rui <rui.zhang@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v2 3/4] ACPI: x86: Move blacklist to x86 folder
Date: Fri, 5 Apr 2024 08:29:20 -0700 [thread overview]
Message-ID: <36bb25c6-bb0b-4a95-936f-0f0333b2d1cf@linux.intel.com> (raw)
In-Reply-To: <ZhAWnOMaIcgXykft@smile.fi.intel.com>
On 4/5/24 8:19 AM, Andy Shevchenko wrote:
> On Fri, Apr 05, 2024 at 07:44:15AM -0700, Kuppuswamy Sathyanarayanan wrote:
>> On 4/4/24 11:23 AM, Andy Shevchenko wrote:
>>> blacklist is built solely for x86, move it to the respective folder.
>> Don't you need #ifdef CONFIG_X86 for acpi_blacklisted() in
>> include/linux/acpi.h
> It's unrelated to this series.
> It was like that before and this series doesn't change this aspect.
>
> AFAICS the API is called from x86 only, that's why it's not a problem,
> but strictly speaking you are right. Feel free to submit a patch.
>
Agree.
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2024-04-05 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 18:23 [PATCH v2 0/4] ACPI: x86: Move x86 stuff into dedicated folder Andy Shevchenko
2024-04-04 18:23 ` [PATCH v2 1/4] ACPI: x86: Introduce a Makefile Andy Shevchenko
2024-04-04 18:23 ` [PATCH v2 2/4] ACPI: x86: Move acpi_cmos_rtc to x86 folder Andy Shevchenko
2024-04-04 18:23 ` [PATCH v2 3/4] ACPI: x86: Move blacklist " Andy Shevchenko
2024-04-05 14:44 ` Kuppuswamy Sathyanarayanan
2024-04-05 15:19 ` Andy Shevchenko
2024-04-05 15:29 ` Kuppuswamy Sathyanarayanan [this message]
2024-04-04 18:23 ` [PATCH v2 4/4] ACPI: x86: Move LPSS " Andy Shevchenko
2024-04-05 14:45 ` [PATCH v2 0/4] ACPI: x86: Move x86 stuff into dedicated folder Kuppuswamy Sathyanarayanan
2024-04-05 15:20 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36bb25c6-bb0b-4a95-936f-0f0333b2d1cf@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.