public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Zhang Rui <rui.zhang@intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v2 0/4] ACPI: x86: Move x86 stuff into dedicated folder
Date: Fri, 5 Apr 2024 07:45:29 -0700	[thread overview]
Message-ID: <aac4b3ea-72dc-4afd-8f1f-06821de953c4@linux.intel.com> (raw)
In-Reply-To: <20240404183448.3310449-1-andriy.shevchenko@linux.intel.com>


On 4/4/24 11:23 AM, Andy Shevchenko wrote:
> Move x86 related modules (which are solely for x86) to the dedicated
> folder.
> Note, there are more modules, but they are related to tables and
> potentially might be used for other architectures in the future.
> Hence touched only non-table related code.

Except the blacklisted patch Nit, rest looks good to me.

Reviewed-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
>
> In v2:
> - fixed acpi_lpss_init() stub visibility (LKP)
>
> Andy Shevchenko (4):
>   ACPI: x86: Introduce a Makefile
>   ACPI: x86: Move acpi_cmos_rtc to x86 folder
>   ACPI: x86: Move blacklist to x86 folder
>   ACPI: x86: Move LPSS to x86 folder
>
>  drivers/acpi/Makefile                            | 7 +------
>  drivers/acpi/internal.h                          | 3 ++-
>  drivers/acpi/x86/Makefile                        | 8 ++++++++
>  drivers/acpi/{ => x86}/blacklist.c               | 2 +-
>  drivers/acpi/{acpi_cmos_rtc.c => x86/cmos_rtc.c} | 2 +-
>  drivers/acpi/{acpi_lpss.c => x86/lpss.c}         | 2 +-
>  6 files changed, 14 insertions(+), 10 deletions(-)
>  create mode 100644 drivers/acpi/x86/Makefile
>  rename drivers/acpi/{ => x86}/blacklist.c (99%)
>  rename drivers/acpi/{acpi_cmos_rtc.c => x86/cmos_rtc.c} (98%)
>  rename drivers/acpi/{acpi_lpss.c => x86/lpss.c} (99%)
>
-- 
Sathyanarayanan Kuppuswamy
Linux Kernel Developer


  parent reply	other threads:[~2024-04-05 14:45 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
2024-04-04 18:23 ` [PATCH v2 4/4] ACPI: x86: Move LPSS " Andy Shevchenko
2024-04-05 14:45 ` Kuppuswamy Sathyanarayanan [this message]
2024-04-05 15:20   ` [PATCH v2 0/4] ACPI: x86: Move x86 stuff into dedicated folder 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=aac4b3ea-72dc-4afd-8f1f-06821de953c4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox