From: skannan@codeaurora.org
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Rajendra Nayak <rjendra@codeaurora.org>,
Amit Kucheria <amit.kucheria@linaro.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
rjwysocki@gmail.com
Subject: Re: [PATCH 1/2] Revert "cpufreq: Remove policy create/remove notifiers"
Date: Fri, 18 May 2018 01:47:40 -0700 [thread overview]
Message-ID: <e86a168756927b9fe4fb1c6bcc4eb198@codeaurora.org> (raw)
In-Reply-To: <CAJZ5v0i_nCj=sBSwrTjxCbL74Q-AwXJb5L2fV1e9SEMYACZC=g@mail.gmail.com>
On 2018-05-18 01:33, Rafael J. Wysocki wrote:
> On Fri, May 18, 2018 at 10:31 AM, <skannan@codeaurora.org> wrote:
>> On 2018-05-18 01:29, Rafael J. Wysocki wrote:
>>>
>>> On Fri, May 18, 2018 at 10:24 AM, Saravana Kannan
>>> <skannan@codeaurora.org> wrote:
>>>>
>>>> This reverts commit f9f41e3ef99ac9d4e91b07634362e393fb929aad.
>>>
>>>
>>> No explanation, no cake. :-)
>>>
>>>> Change-Id: Iddde3ef56c9e5b14dcb14f8737899b85e56f5b43
>>>
>>>
>>> S-o-b missing.
>>
>>
>> Sorry, forgot the S-o-b. But there's a long explanation in the cover
>> letter
>> :)
>
> Cover letters don't go into git repositories, so please move it to the
> patch itself.
Will do. Do you have any opposition to what the series is trying to do?
Thanks,
Saravana
next prev parent reply other threads:[~2018-05-18 8:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 8:24 [PATCH 0/2] Adding support for scaling cache/memory based on CPU frequency Saravana Kannan
2018-05-18 8:24 ` [PATCH 1/2] Revert "cpufreq: Remove policy create/remove notifiers" Saravana Kannan
2018-05-18 8:29 ` Rafael J. Wysocki
2018-05-18 8:31 ` skannan
2018-05-18 8:33 ` Rafael J. Wysocki
2018-05-18 8:47 ` skannan [this message]
2018-05-18 8:59 ` Rafael J. Wysocki
2018-05-18 8:24 ` [PATCH 2/2] PM / devfreq: Generic cpufreq governor Saravana Kannan
2018-05-23 16:58 ` Rob Herring
2018-05-31 21:53 ` Saravana Kannan
[not found] ` <CGME20180518082505epcas2p265038f51fc070a4aada4c692a71ebc3c@epcms1p8>
2018-05-28 6:00 ` MyungJoo Ham
2018-06-05 23:26 ` Saravana Kannan
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=e86a168756927b9fe4fb1c6bcc4eb198@codeaurora.org \
--to=skannan@codeaurora.org \
--cc=amit.kucheria@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjendra@codeaurora.org \
--cc=rjw@rjwysocki.net \
--cc=rjwysocki@gmail.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;
as well as URLs for NNTP newsgroup(s).