[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250409-chirpy-gerbil-of-drizzle-a948dd@sudeepholla>
Date: Wed, 9 Apr 2025 20:16:09 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Linux PM <linux-pm@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Sudeep Holla <sudeep.holla@....com>,
Viresh Kumar <viresh.kumar@...aro.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Mario Limonciello <mario.limonciello@....com>
Subject: Re: [PATCH v1 00/10] cpufreq: cpufreq_update_limits() fix and some
cleanups
On Fri, Mar 28, 2025 at 09:36:05PM +0100, 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.
>
For all the generic changes(i.e. except x86 specific changes)
Acked-by: Sudeep Holla <sudeep.holla@....com>
I also gave it a quick test using scmi-cpufreq on my Juno platform.
Tested-by: Sudeep Holla <sudeep.holla@....com>
--
Regards,
Sudeep
Powered by blists - more mailing lists