From: Suman Anna <s-anna@ti.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Dave Gerlach <d-gerlach@ti.com>, Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] ti-cpufreq: minor fixes/cleanups
Date: Thu, 31 May 2018 17:29:01 -0500 [thread overview]
Message-ID: <c49fce73-ae82-2074-8d9c-c7019fa8fdb4@ti.com> (raw)
In-Reply-To: <2808028.7H1yeuone6@aspire.rjw.lan>
Hi Rafael,
On 05/18/2018 03:19 PM, Rafael J. Wysocki wrote:
> On Friday, May 18, 2018 5:07:12 PM CEST Suman Anna wrote:
>> 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?
>
> You need to resend them I'm afraid, with any tags received so far.
>
> And they won't be picked up if you don't CC linux-pm@vger.kernel.org on
> the submission.
Sorry for the delay, I have reposted the series with all the tags picked
up and CCing the linux-pm list.
regards
Suman
prev parent reply other threads:[~2018-05-31 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 16:49 [PATCH v2 0/2] ti-cpufreq: minor fixes/cleanups Suman Anna
2018-04-02 16:49 ` [PATCH v2 1/2] cpufreq: ti-cpufreq: Fix an incorrect error return value Suman Anna
2018-04-03 4:20 ` Viresh Kumar
2018-04-02 16:49 ` [PATCH v2 2/2] cpufreq: ti-cpufreq: Use devres managed API in probe() Suman Anna
2018-04-03 4:22 ` Viresh Kumar
2018-05-18 15:07 ` [PATCH v2 0/2] ti-cpufreq: minor fixes/cleanups Suman Anna
2018-05-18 20:19 ` Rafael J. Wysocki
2018-05-31 22:29 ` Suman Anna [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c49fce73-ae82-2074-8d9c-c7019fa8fdb4@ti.com \
--to=s-anna@ti.com \
--cc=d-gerlach@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=t-kristo@ti.com \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox