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 3/6] PM / devfreq: Add show_one macro to delete the duplicate code
Date: Mon, 23 Nov 2015 06:33:56 +0000 (GMT) [thread overview]
Message-ID: <741089866.121351448260436496.JavaMail.weblogic@epmlwas06a> (raw)
>
> This patch adds the 'show_one' macro to simplify the duplicate code
> of both max_freq_show() and min_freq_show().
>
> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
Applied.
Thanks.
> ---
> drivers/devfreq/devfreq.c | 20 +++++++++-----------
> 1 file changed, 9 insertions(+), 11 deletions(-)
>
next reply other threads:[~2015-11-23 6:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 6:33 MyungJoo Ham [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-19 8:17 [PATCH 0/6] PM / devfreq: Clean code and add set the freq_table array Chanwoo Choi
2015-11-19 8:17 ` [PATCH 3/6] PM / devfreq: Add show_one macro to delete the duplicate code 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=741089866.121351448260436496.JavaMail.weblogic@epmlwas06a \
--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