From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, rafael@kernel.org,
lenb@kernel.org, ilpo.jarvinen@linux.intel.com,
mario.limonciello@amd.com, mpearson-lenovo@squebb.ca,
W_Armin@gmx.de, arnd@arndb.de, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: acpi: Fix platform profile driver on !acpi platforms
Date: Tue, 10 Jun 2025 16:28:36 +0000 [thread overview]
Message-ID: <174957291699.2454024.8618597246072730689.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250522141410.31315-1-alexghiti@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Rafael J. Wysocki <rafael.j.wysocki@intel.com>:
On Thu, 22 May 2025 16:13:56 +0200 you wrote:
> The platform profile driver is loaded even on platforms that do not have
> acpi enabled. The initialization of the sysfs entries was recently moved
> from platform_profile_register() to the module init call, and those
> entries need acpi_kobj to be initialized which is not the case when acpi
> is disabled.
>
> This results in the following warning:
>
> [...]
Here is the summary with links:
- drivers: acpi: Fix platform profile driver on !acpi platforms
https://git.kernel.org/riscv/c/dd133162c9cf
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-06-10 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 14:13 [PATCH] drivers: acpi: Fix platform profile driver on !acpi platforms Alexandre Ghiti
2025-05-22 14:18 ` Arnd Bergmann
2025-05-22 14:20 ` Mark Pearson
2025-05-22 20:04 ` Armin Wolf
2025-05-23 10:11 ` Alexandre Ghiti
2025-05-23 10:50 ` Rafael J. Wysocki
2025-05-23 14:46 ` Rafael J. Wysocki
2025-05-23 20:01 ` Alexandre Ghiti
2025-05-23 10:44 ` Arnd Bergmann
2025-06-10 16:28 ` patchwork-bot+linux-riscv [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=174957291699.2454024.8618597246072730689.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=W_Armin@gmx.de \
--cc=alexghiti@rivosinc.com \
--cc=arnd@arndb.de \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mario.limonciello@amd.com \
--cc=mpearson-lenovo@squebb.ca \
--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