mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: cpufreq@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	Lists linaro-kernel <linaro-kernel@lists.linaro.org>
Subject: Re: [GIT PULL] ARM: CPUFreq updates for 3.11
Date: Mon, 24 Jun 2013 13:45:15 +0200	[thread overview]
Message-ID: <1662523.HdXbLYrd2q@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpomdnEgDcAExoyN1b4vohHNEg3NDH1mM8NWG8gQoPvff+Q@mail.gmail.com>

On Monday, June 24, 2013 04:40:27 PM Viresh Kumar wrote:
> On 24 June 2013 16:29, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> 
> > In your original series that patch was the last one.  What made you change your
> > mind and put it in front?
> 
> I initially thought that this one would break git bisect (code would
> compile, but would fail) for platforms whose code I have fixed in
> this patchset.
> 
> But that is true only for failure cases, otherwise code would work as
> normal.
> 
> And hence kept this at the top this time.

Well, it should go last.  Also I'd prefer to apply it directly.

Please check my comment in there too.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2013-06-24 11:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24  5:50 Viresh Kumar
2013-06-24 10:49 ` Rafael J. Wysocki
2013-06-24 10:42   ` Viresh Kumar
2013-06-24 10:59     ` Rafael J. Wysocki
2013-06-24 11:10       ` Viresh Kumar
2013-06-24 11:45         ` Rafael J. Wysocki [this message]
2013-06-24 12:50           ` Viresh Kumar
2013-06-24 13:20             ` 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=1662523.HdXbLYrd2q@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=cpufreq@vger.kernel.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --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®