From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org,
robin.randhawa@arm.com, Steve.Bannister@arm.com,
Liviu.Dudau@arm.com, charles.garcia-tobin@arm.com
Subject: Re: [PATCH V3 2/4] cpufreq: governor: Implement per policy instances of governors
Date: Fri, 22 Mar 2013 12:55:09 +0100 [thread overview]
Message-ID: <1483775.d1txvSJx9o@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpomDK+FQvhZsy672P+Q4U1s2AGtJ2QizFTaNqjMRh19G0g@mail.gmail.com>
On Friday, March 22, 2013 07:50:54 AM Viresh Kumar wrote:
> On 22 March 2013 05:14, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Wednesday, March 20, 2013 10:59:13 AM Viresh Kumar wrote:
>
> >> I have queued all patches i had for 3.10 here:
> >>
> >> http://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=shortlog;h=refs/heads/for-3.10
> >
> > OK, applied these to linux-pm.git/bleeding-edge.
>
> Thanks.
>
> > At the moment bleeding-edge and linux-next diverged slightly on cpufreq, but
> > I hope the bleeding-edge material won't cause build problems to occur, so I'll
> > be able to move it to linux-next shortly.
>
> There shouldn't be any build problems not because i have done all build testing
> properly BUT because my tree is under continuously surveillance by Fengguang's
> bot. And any problem with my branches is reported very early :)
>
> >> commit f02fca9a2478088c4f7dadf82d998ae007a56285
> >> Author: Viresh Kumar <viresh.kumar@linaro.org>
> >> Date: Wed Mar 20 10:50:33 2013 +0530
> >>
> >> fixup! cpufreq: governor: Implement per policy instances of governors
> >
> > I'd actually prefer you to post complete updated patches instead of these
> > fixups. They are real PITA for me and probably for everybody else trying
> > to follow the cpufreq development recently.
>
> Hmm... I always thought fixups are way easy to review (and i still
> believe that's
> true) as they just contain what got changed and so people don't have to review
> whole patch again.
They won't have to if you write in the preamble what the differences from
previous versions are.
> BUT people who are looking for complete patches to apply
> would be annoyed by this and hence i always show them path of my repo
> where they can find it.
The problem with this approach is that the complete patches never make it to
the mailing lists and people have problems with connecting commits to
previously posted patches.
Moreover, it is *much* more convenient to me to take patches from kernel.org
patchwork than from your repos, with all due respect.
> So, what i may do is, post fixups and then resend
> patches. So that reviewer knows what changed and others can have complete
> patches too.
Sure, that will work too.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-03-22 11:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 7:37 [PATCH V3 0/4] CPUFreq: " Viresh Kumar
2013-03-04 7:37 ` [PATCH V3 1/4] cpufreq: Add per policy governor-init/exit infrastructure Viresh Kumar
2013-03-04 7:37 ` [PATCH V3 2/4] cpufreq: governor: Implement per policy instances of governors Viresh Kumar
2013-03-20 5:29 ` Viresh Kumar
2013-03-21 23:44 ` Rafael J. Wysocki
2013-03-22 2:20 ` Viresh Kumar
2013-03-22 11:55 ` Rafael J. Wysocki [this message]
2013-03-22 11:51 ` Viresh Kumar
2013-03-22 12:11 ` Rafael J. Wysocki
2013-03-22 12:05 ` Viresh Kumar
2013-03-26 15:20 ` Jacob Shin
2013-03-26 19:32 ` Viresh Kumar
2013-03-26 19:48 ` Jacob Shin
2013-03-27 4:29 ` Viresh Kumar
2013-03-27 10:04 ` Viresh Kumar
2013-03-27 11:35 ` Viresh Kumar
2013-03-27 14:37 ` Viresh Kumar
2013-03-04 7:37 ` [PATCH V3 3/4] cpufreq: Get rid of "struct global_attr" Viresh Kumar
2013-03-04 7:37 ` [PATCH V3 4/4] cpufreq: Add Kconfig option to enable/disable have_multiple_policies Viresh Kumar
2013-03-11 23:38 ` Rafael J. Wysocki
2013-03-12 0:55 ` Viresh Kumar
2013-03-13 21:41 ` Rafael J. Wysocki
2013-03-14 3:09 ` Viresh Kumar
2013-03-20 0:20 ` Rafael J. Wysocki
2013-03-20 4:23 ` Viresh Kumar
2013-03-20 5:16 ` Viresh Kumar
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=1483775.d1txvSJx9o@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=charles.garcia-tobin@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robin.randhawa@arm.com \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®