public inbox for cpufreq@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
	rjw@sisk.pl, linux ARM <linux-arm-kernel@lists.infradead.org>,
	cpufreq@vger.kernel.org
Subject: Re: [PATCH 43 0/3] Kirkwoode cpufreq driver
Date: Fri, 1 Feb 2013 15:37:52 +0100	[thread overview]
Message-ID: <20130201143752.GQ17242@lunn.ch> (raw)
In-Reply-To: <CAKohpokjN8kx9Tan=wG4d0tdicWpb6DLN7o+rbX5f9oppJK7bA@mail.gmail.com>

On Fri, Feb 01, 2013 at 08:04:27PM +0530, Viresh Kumar wrote:
> On 1 February 2013 20:01, Andrew Lunn <andrew@lunn.ch> wrote:
> > This patchset adds a cpufreq driver for Marvell Kirkwood SoCs.
> >
> > The changes to kirkwood_defconfig enable it and set the default
> > governor to ondemand.
> 
> Wow! [PATCH 43 0/3] :)
> It looks you are adding v4 manually to every patch? 

No, I just edited the cover note. For the others i used --subject=...

    Andrew

      reply	other threads:[~2013-02-01 14:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 14:31 [PATCH 43 0/3] Kirkwoode cpufreq driver Andrew Lunn
2013-02-01 14:31 ` [PATCH v4 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs Andrew Lunn
2013-02-01 15:40   ` Viresh Kumar
2013-02-03 14:14   ` Shawn Guo
2013-02-01 14:31 ` [PATCH v4 2/3] arm: kirkwood: Instantiate cpufreq driver Andrew Lunn
2013-02-01 14:31 ` [PATCH v4 3/3] arm: kirkwood: Enable cpufreq and ondemand on kirkwood_defconfig Andrew Lunn
2013-02-01 14:34 ` [PATCH 43 0/3] Kirkwoode cpufreq driver Viresh Kumar
2013-02-01 14:37   ` Andrew Lunn [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=20130201143752.GQ17242@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=cpufreq@vger.kernel.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=rjw@sisk.pl \
    --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