[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9d8affc8-a88c-477b-9ee3-c0ec52e00b0e@web.de>
Date: Sat, 3 Jan 2026 14:16:12 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Jianhao Xu <jianhao.xu@....edu.cn>, Zilin Guan <zilin@....edu.cn>,
platform-driver-x86@...r.kernel.org, Hans de Goede <hansg@...nel.org>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] platform/x86/amd: Fix memory leak in wbrf_record()
…> +++ b/drivers/platform/x86/amd/wbrf.c
> @@ -39,11 +39,11 @@ static const guid_t wifi_acpi_dsm_guid =
> */
> static BLOCKING_NOTIFIER_HEAD(wbrf_chain_head);
>
> +DEFINE_FREE(acpi_object, union acpi_object *, if (_T) ACPI_FREE(_T))
> +
> static int wbrf_record(struct acpi_device *adev, uint8_t action, struct wbrf_ranges_in_out *in)
> {
…
Is there a need to move such a special macro call into an other source (or header) file?
Regards,
Markus
Powered by blists - more mailing lists