[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0i34XTWzV-PnrC1JZ7sTWcRDF9rDsoZ0N+GEHOH9zeWfw@mail.gmail.com>
Date: Wed, 23 Nov 2022 19:30:25 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Wang ShaoBo <bobo.shaobowang@...wei.com>
Cc: rafael.j.wysocki@...el.com, rafael@...nel.org, lenb@...nel.org,
yu.c.chen@...el.com, linux-acpi@...r.kernel.org,
guohanjun@...wei.com, liwei391@...wei.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] change to use ACPI_FREE() to free the ACPI memory
On Fri, Nov 18, 2022 at 7:33 AM Wang ShaoBo <bobo.shaobowang@...wei.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!
Powered by blists - more mailing lists