From: "lihuisong (C)" <lihuisong@huawei.com>
To: <rafael@kernel.org>, <lenb@kernel.org>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <jonathan.cameron@huawei.com>,
<zhanjie9@hisilicon.com>, <zhenglifeng1@huawei.com>,
<yubowen8@huawei.com>, <liuyonglong@huawei.com>
Subject: Re: [PATCH v3 0/2] ACPI: processor: idle: Optimize acpi idle driver registration
Date: Tue, 19 Aug 2025 19:07:41 +0800 [thread overview]
Message-ID: <6b65f2a1-7906-4659-a254-3cbbc9ba8bf1@huawei.com> (raw)
In-Reply-To: <20250728070612.1260859-1-lihuisong@huawei.com>
Kindly ping for review.
在 2025/7/28 15:06, Huisong Li 写道:
> This series fix a memory leak issue and optimize the registration of
> acpi idle driver to enhance its readability.
>
> ---
> changelog:
> v3:
> * use a separate patch to fix memory leak.
> * change the return value of the new function to void.
> * change log level to debug on failure path.
> v2:
> * register cpuidle driver in advance when all of the CPUs have been
> brought up.
> https://patchwork.kernel.org/project/linux-acpi/patch/20250723121034.3685996-1-lihuisong@huawei.com/
> v1:
> https://patchwork.kernel.org/project/linux-acpi/patch/20250619061327.1674384-1-lihuisong@huawei.com/
>
> Huisong Li (2):
> ACPI: processor: idle: Fix memory leak when register cpuidle device
> failed
> ACPI: processor: idle: Optimize acpi idle driver registration
>
> drivers/acpi/processor_driver.c | 3 ++
> drivers/acpi/processor_idle.c | 67 ++++++++++++++++++++++-----------
> include/acpi/processor.h | 8 ++++
> 3 files changed, 55 insertions(+), 23 deletions(-)
>
prev parent reply other threads:[~2025-08-19 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 7:06 Huisong Li
2025-07-28 7:06 ` [PATCH v3 1/2] ACPI: processor: idle: Fix memory leak when register cpuidle device failed Huisong Li
2025-08-22 19:27 ` Rafael J. Wysocki
2025-07-28 7:06 ` [PATCH v3 2/2] ACPI: processor: idle: Optimize acpi idle driver registration Huisong Li
2025-08-23 16:13 ` Rafael J. Wysocki
2025-08-25 6:05 ` lihuisong (C)
2025-08-19 11:07 ` lihuisong (C) [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=6b65f2a1-7906-4659-a254-3cbbc9ba8bf1@huawei.com \
--to=lihuisong@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=rafael@kernel.org \
--cc=yubowen8@huawei.com \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@huawei.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
all inboxes | Powered by JetHome®