From: Javi Merino <javi.merino@arm.com>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
최찬우 <cw00.choi@samsung.com>,
"rufus.hamade@imgtec.com" <rufus.hamade@imgtec.com>,
"edubezval@gmail.com" <edubezval@gmail.com>
Subject: Re: [PATCH v5 5/5] PM / devfreq: drop comment about thermal setting max_freq
Date: Thu, 27 Aug 2015 13:52:43 +0100 [thread overview]
Message-ID: <20150827125243.GF5653@e104805> (raw)
In-Reply-To: <1457392753.243291440673119677.JavaMail.weblogic@ep2mlwas06c>
On Thu, Aug 27, 2015 at 11:58:39AM +0100, MyungJoo Ham wrote:
> > The thermal infrastructure should use the devfreq cooling device, which
> > uses the OPP library to disable OPPs as necessary.
> >
> > Fix a couple of typos in the same comment while we are at it.
> >
> > Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
> > Signed-off-by: Javi Merino <javi.merino@arm.com>
>
> Your patches (1/5, 5/5) are already merged in https://git.kernel.org/cgit/linux/kernel/git/mzx/devfreq.git
> and will be "pull-request"ed with other patches later.
>
> Do your "V5" patches have updates from last patches?
No they haven't. I should have based this series on top of your
branch. I'll do that in the future.
Sorry for that,
Javi
next prev parent reply other threads:[~2015-08-27 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 10:58 [PATCH v5 5/5] PM / devfreq: drop comment about thermal setting max_freq MyungJoo Ham
2015-08-27 12:52 ` Javi Merino [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-27 10:55 [PATCH v5 0/5] Devfreq cooling device Javi Merino
2015-08-27 10:55 ` [PATCH v5 5/5] PM / devfreq: drop comment about thermal setting max_freq Javi Merino
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=20150827125243.GF5653@e104805 \
--to=javi.merino@arm.com \
--cc=cw00.choi@samsung.com \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rufus.hamade@imgtec.com \
/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