public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hanjun Guo <guohanjun@huawei.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>
Cc: Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	<linux-acpi@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Hanjun Guo <guohanjun@huawei.com>
Subject: [PATCH 0/3] cleanups for ARM64 ACPI
Date: Thu, 8 Aug 2024 21:15:19 +0800	[thread overview]
Message-ID: <20240808131522.1032431-1-guohanjun@huawei.com> (raw)

Remove some leftover functions in asm/acpi.h, and ACPI NUMA
code are not strictly arch specific, move them to drivers/acpi/arm64/.

Hanjun Guo (3):
  ARM64: ACPI: Remove the leftover acpi_init_cpus()
  ARM64: ACPI: Remove the leftover arm64_acpi_numa_init()
  ARM64: ACPI: Move the NUMA code to drivers/acpi/arm64/

 arch/arm64/include/asm/acpi.h                        | 12 ------------
 arch/arm64/kernel/Makefile                           |  1 -
 drivers/acpi/arm64/Makefile                          |  1 +
 .../arm64/kernel => drivers/acpi/arm64}/acpi_numa.c  |  0
 include/linux/acpi.h                                 |  4 ++++
 5 files changed, 5 insertions(+), 13 deletions(-)
 rename {arch/arm64/kernel => drivers/acpi/arm64}/acpi_numa.c (100%)

-- 
2.25.1


             reply	other threads:[~2024-08-08 13:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 13:15 Hanjun Guo [this message]
2024-08-08 13:15 ` [PATCH 1/3] ARM64: ACPI: Remove the leftover acpi_init_cpus() Hanjun Guo
2024-08-08 13:15 ` [PATCH 2/3] ARM64: ACPI: Remove the leftover arm64_acpi_numa_init() Hanjun Guo
2024-08-08 13:15 ` [PATCH 3/3] ARM64: ACPI: Move the NUMA code to drivers/acpi/arm64/ Hanjun Guo
2024-08-08 23:49   ` kernel test robot
2024-08-09  7:21   ` Sudeep Holla
2024-08-09 10:45     ` Hanjun Guo

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=20240808131522.1032431-1-guohanjun@huawei.com \
    --to=guohanjun@huawei.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=will@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