From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Re: [PATCH v4 1/4] PM / devfreq: Fix the wrong description for userspace governor
Date: Tue, 31 Jan 2017 04:51:59 +0000 [thread overview]
Message-ID: <20170131045159epcms1p251b95eb0af135c4620c7b435b4eda039@epcms1p2> (raw)
In-Reply-To: <20170124034211epcms1p6ded0f600506896af5bdf09e9afd6eb94@epcms1p6>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
> On Tue, Jan 24, 2017 at 4:42 AM, MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
> >> This patch fixes the wrong description of governor_userspace.c
> >> and removes the unneeded blank line.
> >>
> >> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
> >> ---
> >
> > Applied in for-next
>
>
> Quite frankly I'm not entirely sure what's going on in the devfreq land.
>
> Some patches are ACKed by you, some of them are applied and it is hard
> to say what the rule is.
>
> Besides, it is quite late in the cycle, so it would be nice to receive
> a pull request for the devfreq material already collected for 4.11.
>
> Thanks,
> Rafael
- The patches that change ABI is being delayed
for further discussions with Chanwoo.
- The patches that change mechanisms of handling passive governor
differently in devfreq.c require further updates from Chanwoo;
so they are being not applied for now as well.
If it appears that those two patchset are not going to make in time
(mid this week), I'll send out pull-request for 4.11 without them.
Cheers,
MyungJoo
next prev parent reply other threads:[~2017-01-31 5:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170123033151epcas5p3349612f1f97c31d85d90604cbca8a19d@epcas5p3.samsung.com>
2017-01-23 3:31 ` [PATCH v4 0/4] PM / devfreq: Update the devfreq and devfreq-event device Chanwoo Choi
[not found] ` <CGME20170123033152epcas5p34efc72ecd1afb21efca58421ab41cbc6@epcas5p3.samsung.com>
2017-01-23 3:31 ` [PATCH v4 3/4] PM / devfreq: Simplify the sysfs name of " Chanwoo Choi
[not found] ` <CGME20170123033152epcas5p3c2d5ced0fcce359e8fd2d0576462c029@epcas5p3.samsung.com>
2017-01-23 3:31 ` [PATCH v4 4/4] PM / devfreq: Modify the device name as devfreq[X] for sysfs Chanwoo Choi
[not found] ` <CGME20170123033151epcas5p3a484d70bbdef282b92eb8d97d912e75c@epcas5p3.samsung.com>
2017-01-23 3:31 ` [PATCH v4 1/4] PM / devfreq: Fix the wrong description for userspace governor Chanwoo Choi
2017-01-24 3:42 ` MyungJoo Ham
2017-01-30 10:44 ` Rafael J. Wysocki
2017-01-31 4:51 ` MyungJoo Ham [this message]
[not found] ` <CGME20170123033151epcas5p341aa786474af221e390eed87ea48381e@epcas5p3.samsung.com>
2017-01-23 3:31 ` [PATCH v4 2/4] PM / devfreq: exynos-ppmu: Show the registred device for ppmu device Chanwoo Choi
2017-01-24 3:42 ` MyungJoo Ham
2017-01-24 8:15 ` 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=20170131045159epcms1p251b95eb0af135c4620c7b435b4eda039@epcms1p2 \
--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 \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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
all inboxes | Powered by JetHome®