From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Wang ShaoBo <bobo.shaobowang@huawei.com>
Cc: rafael.j.wysocki@intel.com, rafael@kernel.org, lenb@kernel.org,
yu.c.chen@intel.com, linux-acpi@vger.kernel.org,
guohanjun@huawei.com, liwei391@huawei.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] change to use ACPI_FREE() to free the ACPI memory
Date: Wed, 23 Nov 2022 19:30:25 +0100 [thread overview]
Message-ID: <CAJZ5v0i34XTWzV-PnrC1JZ7sTWcRDF9rDsoZ0N+GEHOH9zeWfw@mail.gmail.com> (raw)
In-Reply-To: <20221118063219.2612473-1-bobo.shaobowang@huawei.com>
On Fri, Nov 18, 2022 at 7:33 AM Wang ShaoBo <bobo.shaobowang@huawei.com> wrote:
>
> acpi_evaluate_dsm_typed()/acpi_evaluate_dsm() should be coupled with
> ACPI_FREE() to free the ACPI memory, because we need to track the
> allocation of acpi_object when ACPI_DBG_TRACK_ALLOCATIONS enabled,
> so use ACPI_FREE() instead of kfree().
>
> Wang ShaoBo (2):
> ACPI: pfr_telemetry: use ACPI_FREE() to free acpi_object
> ACPI: pfr_update: use ACPI_FREE() to free acpi_object
>
> drivers/acpi/pfr_telemetry.c | 6 +++---
> drivers/acpi/pfr_update.c | 6 +++---
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> --
Both applied as 6.2 material, thanks!
prev parent reply other threads:[~2022-11-23 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 6:32 [PATCH 0/2] change to use ACPI_FREE() to free the ACPI memory Wang ShaoBo
2022-11-18 6:32 ` [PATCH 1/2] ACPI: pfr_telemetry: use ACPI_FREE() to free acpi_object Wang ShaoBo
2022-11-18 11:21 ` Chen Yu
2022-11-18 6:32 ` [PATCH 2/2] ACPI: pfr_update: " Wang ShaoBo
2022-11-18 11:23 ` Chen Yu
2022-11-23 18:30 ` Rafael J. Wysocki [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=CAJZ5v0i34XTWzV-PnrC1JZ7sTWcRDF9rDsoZ0N+GEHOH9zeWfw@mail.gmail.com \
--to=rafael@kernel.org \
--cc=bobo.shaobowang@huawei.com \
--cc=guohanjun@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=rafael.j.wysocki@intel.com \
--cc=yu.c.chen@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;
as well as URLs for NNTP newsgroup(s).