[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c817bf2d-9dfc-4685-8b7d-82e74f594a1b@amd.com>
Date: Tue, 1 Apr 2025 11:57:45 -0500
From: Mario Limonciello <mario.limonciello@....com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Linux PM <linux-pm@...r.kernel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Sudeep Holla <sudeep.holla@....com>
Subject: Re: [PATCH v1 00/10] cpufreq: cpufreq_update_limits() fix and some
cleanups
On 3/28/2025 3:36 PM, Rafael J. Wysocki wrote:
> Hi Everyone,
>
> This series of patches consists of a fix for a possible (and actually happening
> in some cases) NULL pointer dereference in cpufreq_update_limits() (patch
> [01/10]) and a bunch of tangentially related fixes inspired by it, mostly about
> using __free() for cleanup and locking guards.
>
> The first patch is definitely for 6.15, but the rest is rather 6.16 material.
>
> Please refer to the individual patch changelogs for more information.
>
> Thanks!
>
>
>
It's a great set of cleanups, makes the code a lot easier to follow.
For the series:
Reviewed-by: Mario Limonciello <mario.limonciello@....com>
Powered by blists - more mailing lists