From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: 최찬우 <cw00.choi@samsung.com>, 박경민 <kyungmin.park@samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 0/6] PM / devfreq: Clean code and add set the freq_table array
Date: Thu, 19 Nov 2015 08:46:08 +0000 (GMT) [thread overview]
Message-ID: <1678444918.1189481447922768056.JavaMail.weblogic@ep2mlwas06b> (raw)
> This patch-set clean the code for both devfreq and devfreq-event framework
> and add the 'freq_table' for devfreq device. After initializing the
> 'freq_table', the 'trans_stat' sysfs provide the appropriate information.
Chanwoo,
Are these the same patches in your git, https://git.kernel.org/cgit/linux/kernel/git/chanwoo/linux.git/log/?h=devfreq-next ?
Cheers,
MyungJoo.
next reply other threads:[~2015-11-19 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 8:46 MyungJoo Ham [this message]
2015-11-19 9:38 ` [PATCH 0/6] PM / devfreq: Clean code and add set the freq_table array Chanwoo Choi
-- strict thread matches above, loose matches on Subject: below --
2015-11-19 8:17 Chanwoo Choi
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=1678444918.1189481447922768056.JavaMail.weblogic@ep2mlwas06b \
--to=myungjoo.ham@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.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