From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v1] ACPI: Declare acpi_blacklisted() only if CONFIG_X86 is enabled
Date: Sun, 28 Apr 2024 21:06:34 -0700 [thread overview]
Message-ID: <228f5064-bf3d-4872-bcf7-b941f001d9dd@linux.intel.com> (raw)
In-Reply-To: <ZiexZnmbLqPy11d1@smile.fi.intel.com>
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@linux.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
prev parent reply other threads:[~2024-04-29 4:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 6:33 [PATCH v1] ACPI: Declare acpi_blacklisted() only if CONFIG_X86 is enabled Kuppuswamy Sathyanarayanan
2024-04-08 14:53 ` Andy Shevchenko
2024-04-08 15:42 ` Kuppuswamy Sathyanarayanan
2024-04-08 15:53 ` Andy Shevchenko
2024-04-22 16:37 ` Rafael J. Wysocki
2024-04-23 13:02 ` Andy Shevchenko
2024-04-29 4:06 ` Kuppuswamy Sathyanarayanan [this message]
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=228f5064-bf3d-4872-bcf7-b941f001d9dd@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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).