From: Chanwoo Choi <cw00.choi@samsung.com>
To: myungjoo.ham@samsung.com, Kyungmin Park <kyungmin.park@samsung.com>
Cc: "rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] PM / devfreq: Move struct devfreq_governor to devfreq directory
Date: Fri, 07 Apr 2017 15:48:34 +0900 [thread overview]
Message-ID: <58E73642.9040104@samsung.com> (raw)
In-Reply-To: <20170407064133epcms1p6daefde5d8ca9e1253c51b0bd3bc23f2d@epcms1p6>
Hi,
On 2017년 04월 07일 15:41, MyungJoo Ham wrote:
>> This patch moves the struct devfreq_governor from header file
>> to the devfreq directory because this structure is private data
>> and it have to be only accessed by the devfreq core.
>>
>> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
>> ---
>> drivers/devfreq/governor.h | 29 +++++++++++++++++++++++++++++
>> include/linux/devfreq.h | 30 +-----------------------------
>> 2 files changed, 30 insertions(+), 29 deletions(-)
>>
>
> Where have you based on the commit?
> It's not appliable to 4.11-rc5.
When I applied it to 4.11-rc5, there is no any conflict.
I used the 'git am' command. Also, As I knew,
after releasing the 4.11-rc1, there was no patches
related to both drivers/devfreq/governor.h and include/linux/devfreq.h
--
Best Regards,
Chanwoo Choi
Samsung Electronics
prev parent reply other threads:[~2017-04-07 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170406041937epcas1p1b5cd8e13bf4049e1e4e5ff4d2b1b75b1@epcas1p1.samsung.com>
2017-04-06 4:19 ` [PATCH] PM / devfreq: Move struct devfreq_governor to devfreq directory Chanwoo Choi
2017-04-07 6:41 ` MyungJoo Ham
2017-04-07 6:48 ` Chanwoo Choi [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=58E73642.9040104@samsung.com \
--to=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rafael.j.wysocki@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.