From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: myungjoo.ham@gmail.com
Cc: Linux PM list <linux-pm@vger.kernel.org>,
rafael.j.wysocki@intel.com, Chanwoo Choi <cw00.choi@samsung.com>
Subject: Re: [GIT PULL] devfreq for next-RC
Date: Thu, 26 Nov 2015 23:48:11 +0100 [thread overview]
Message-ID: <7258636.bTrShIYD0P@vostro.rjw.lan> (raw)
In-Reply-To: <CAJ0PZbQ2Wh6kEjRjGfHhLLsnTcLcxb_iBn9p9auC2V+WTjgcQw@mail.gmail.com>
On Thursday, November 26, 2015 10:51:18 PM MyungJoo Ham wrote:
> 6 of the 8 patches are fixes or style-updates.
Style updates are not fixes, are they?
> Other 2 of 8 (PM / devfreq: Set the freq_table of devfreq device,
> MAINTAINERS: Add devfreq-event entry)
> are small updates (the first of the two may be seen as a fix to follow
> the given API semantics though)
>
> Do you want to pull the 6 clearly-fixes only for the RC?
The only type of material I want to push for -rc4 or later is fixes. No style
updates now in particular, please.
And generally, if there's anything that can wait for the next merge window,
there's no reason to push it today.
So please let me know which of the commits in your branch are urgent in
your opinion and I'll put them into a separate branch and queue them up
for -rc4.
The rest will wait.
Thanks,
Rafael
> On Thu, Nov 26, 2015 at 10:58 PM, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> > On Thursday, November 26, 2015 02:14:40 AM MyungJoo Ham wrote:
> >> Dear Rafael,
> >>
> >> Here goes the pull reqest for next 4.4 RCx.
> >>
> >>
> >> Cheers,
> >> MyungJoo
> >>
> >> The following changes since commit 1ec218373b8ebda821aec00bb156a9c94fad9cd4:
> >>
> >> Linux 4.4-rc2 (2015-11-22 16:45:59 -0800)
> >>
> >> are available in the git repository at:
> >>
> >> https://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git tags/pull_req_20151126
> >>
> >> for you to fetch changes up to 38bb853595404cdd2210268dd508ce303ab836e5:
> >>
> >> MAINTAINERS: Add devfreq-event entry (2015-11-26 10:54:18 +0900)
> >>
> >> ----------------------------------------------------------------
> >> Pull request for Rafael on 2015-11-26. Based on 4.4-rc2
> >>
> >> ----------------------------------------------------------------
> >> Chanwoo Choi (7):
> >> PM / devfreq: event: Remove the error log of devfreq_event_get_edev_by_phandle()
> >> PM / devfreq: event: Fix the error and warning from script/checkpatch.pl
> >> PM / devfreq: Add show_one macro to delete the duplicate code
> >> PM / devfreq: Set the freq_table of devfreq device
> >> PM / devfreq: Modify the indentation of trans_stat sysfs for readability
> >> MAINTAINERS: Add missing git repository and directory for devfreq
> >> MAINTAINERS: Add devfreq-event entry
> >>
> >> MyungJoo Ham (1):
> >> PM / devfreq: Do not show statistics if it's not ready.
> >>
> >> MAINTAINERS | 13 +++++++
> >> drivers/devfreq/devfreq-event.c | 16 +++------
> >> drivers/devfreq/devfreq.c | 78 ++++++++++++++++++++++++++++++++---------
> >> include/linux/devfreq.h | 2 +-
> >> 4 files changed, 81 insertions(+), 28 deletions(-)
> >
> > Is this really 4.4-rc material?
> >
> > We're quite late in the cycle and I'm not willing to push anything more than
> > fixes to Linus at this point.
> >
> > I can pull this and queue it up for v4.5 if that works for you, though.
> >
> > Thanks,
> > Rafael
> >
>
>
>
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2015-11-26 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 2:14 [GIT PULL] devfreq for next-RC MyungJoo Ham
2015-11-26 13:58 ` Rafael J. Wysocki
2015-11-26 13:51 ` MyungJoo Ham
2015-11-26 22:48 ` Rafael J. Wysocki [this message]
2015-11-27 10:47 ` MyungJoo Ham
-- strict thread matches above, loose matches on Subject: below --
2016-01-14 2:11 Re2: " MyungJoo Ham
2016-01-15 0:48 ` Rafael J. Wysocki
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=7258636.bTrShIYD0P@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=cw00.choi@samsung.com \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox