From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Chanwoo Choi <cw00.choi@samsung.com>,
Saravana Kannan <skannan@codeaurora.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Kyungmin Park <kyungmin.park@samsung.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Re: [PATCH v3] PM / devfreq: Restart previous governor if new governor fails to start
Date: Tue, 11 Dec 2018 16:18:18 +0900 [thread overview]
Message-ID: <20181211071818epcms1p30d107ed61043d39b38960ef1616282a0@epcms1p3> (raw)
In-Reply-To: <5C0F4C9A.8030607@samsung.com>
> Hi Saravana,
>
> The devfreq git repo is maintained by Myungjoo Ham.
> you can check it on MAINTAINERS file.
>
> I think that you better to resend mail to mainline
> with my reviewed tag because the devfreq core could be modified
> and then merge conflict might be happen when apply this patch.
>
> Regards,
> Chanwoo Choi
>
> On 2018년 12월 08일 05:29, Saravana Kannan wrote:
> >
> > On 11/9/16 4:10 PM, Chanwoo Choi wrote:
> >> After fixing the bug of devfreq_add_device(),
> >> I'll remove the unneeded 'if statement' of prev_governor in governor_store.
> >
> > It's been 2 years and this patch still hasn't been picked up. Can we please pick this up and get this into the next kernel release?
> >
> > Thanks,
> >
> > Saravana
> >
If that's already 2 years old, please rebase, test to see if that's
still valid with today's kernel, and resubmit.
Sorry for missing it, right now, after 2 years,
I just can't remember this one.
Cheers,
MyungJoo
prev parent reply other threads:[~2018-12-11 7:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161026191715epcas1p311c2c626563a736e14c83fb0504c099e@epcas1p3.samsung.com>
2016-10-26 19:17 ` [PATCH v3] PM / devfreq: Restart previous governor if new governor fails to start Saravana Kannan
2016-10-27 0:06 ` Chanwoo Choi
2016-11-07 18:57 ` Saravana Kannan
2016-11-08 9:02 ` Chanwoo Choi
2016-11-08 20:52 ` Saravana Kannan
2016-11-09 1:33 ` Chanwoo Choi
2016-11-09 2:36 ` Chanwoo Choi
2016-11-09 2:38 ` Chanwoo Choi
2016-11-09 20:34 ` Saravana Kannan
2016-11-10 0:10 ` Chanwoo Choi
2016-11-11 23:25 ` Saravana Kannan
2016-11-12 2:17 ` Chanwoo Choi
2016-11-12 2:18 ` Chanwoo Choi
2018-12-07 20:29 ` Saravana Kannan
2018-12-11 5:35 ` Chanwoo Choi
[not found] ` <CGME20161026191715epcas1p311c2c626563a736e14c83fb0504c099e@epcms1p3>
2018-12-11 7:18 ` MyungJoo Ham [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=20181211071818epcms1p30d107ed61043d39b38960ef1616282a0@epcms1p3 \
--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=rjw@rjwysocki.net \
--cc=skannan@codeaurora.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;
as well as URLs for NNTP newsgroup(s).