[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ffbb49c3-229b-df20-ca0d-c49822fcdaf2@ti.com>
Date: Fri, 18 May 2018 10:07:12 -0500
From: Suman Anna <s-anna@...com>
To: Viresh Kumar <viresh.kumar@...aro.org>
CC: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Dave Gerlach <d-gerlach@...com>, Tero Kristo <t-kristo@...com>,
<linux-omap@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/2] ti-cpufreq: minor fixes/cleanups
On 04/02/2018 11:49 AM, Suman Anna wrote:
> Hi Viresh,
>
> Please find the updated series replacing the previous patch [1] fixing
> couple of issues in the TI CPUFreq driver. I have split up the patches
> as per your comments on v1. Final code diff remains the same as before.
>
> regards
> Suman
>
> [1] https://patchwork.kernel.org/patch/10308925/
>
> Suman Anna (2):
> cpufreq: ti-cpufreq: Fix an incorrect error return value
> cpufreq: ti-cpufreq: Use devres managed API in probe()
Gentle reminder, I don't see these patches in -next. Who is picking up
these patches?
regards
Suman
>
> drivers/cpufreq/ti-cpufreq.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
Powered by blists - more mailing lists