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: Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
	Patch Tracking <patches@linaro.org>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 Resend 0/2] CPUFreq Cleanup Part IV
Date: Thu, 31 Oct 2013 00:07:59 +0100	[thread overview]
Message-ID: <34590053.bi5BTSMqtz@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpokMB+kEQmX-qHJF1NegnA0xvo6+A3HxbDjrpca3yuBEfA@mail.gmail.com>

On Thursday, October 31, 2013 03:57:27 AM Viresh Kumar wrote:
> On 31 October 2013 03:23, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > [2/2] doesn't apply for me cleanly on top of the big/little changes.
> >
> > Care to rebase on top of the new bleeding-edge I've just pushed?
> 
> Done.. Please find attached..

Well, this is the last your patch from an attachment I'm ever going to
apply.  Please don't bother to send any of these to me in the future.

Thanks!

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

  reply	other threads:[~2013-10-30 22:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 13:26 Viresh Kumar
2013-10-29 13:26 ` [PATCH V2 Resend 1/2] cpufreq: distinguish drivers that do asynchronous notifications Viresh Kumar
2013-10-29 13:26 ` [PATCH V2 Resend 2/2] cpufreq: move freq change notifications to cpufreq core Viresh Kumar
2013-10-30 21:53 ` [PATCH V2 Resend 0/2] CPUFreq Cleanup Part IV Rafael J. Wysocki
2013-10-30 22:27   ` Viresh Kumar
2013-10-30 23:07     ` Rafael J. Wysocki [this message]
2013-10-30 22:56       ` 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=34590053.bi5BTSMqtz@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=cpufreq@vger.kernel.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=patches@linaro.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®