cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: cpufreq@www.linux.org.uk
Subject: Re: cpufreq/linux/arch/arm/mach-sa1100 cpu-sa1100.c, 1.5,
Date: Tue, 31 Aug 2004 23:23:58 +0100	[thread overview]
Message-ID: <20040831222358.GA19600@redhat.com> (raw)
In-Reply-To: <20040830171607.C22480@flint.arm.linux.org.uk>

On Mon, Aug 30, 2004 at 05:16:07PM +0100, Russell King wrote:
 > On Mon, Aug 30, 2004 at 05:08:31PM +0200, Dominik Brodowski wrote:
 > > On Mon, Aug 30, 2004 at 03:29:54PM +0100, Russell King wrote:
 > > > Obviously given this information, this flag needs to be removed from ARM.
 > > > If ARM is the only user, then the flag and associated code needs to be
 > > > completely removed.
 > > 
 > > Who shall "push" this patch upstreams? Dave or Russell?
 > 
 > The patch looks good, thanks.
 > 
 > I think Dave would be better - Dave has been pushing most cpufreq stuff
 > to Linus anyway.  Since this is a bug fix rather than a feature, it's
 > definite 2.6.9-rc material.

Merged. I've a handful of other small bits I'm about to merge,
and then I'll send Linus a pull request tonight. Should make it in for -rc2
unless Linus surprises me 8-).

		Dave

      reply	other threads:[~2004-08-31 22:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-29 12:49 cpufreq/linux/arch/arm/mach-sa1100 cpu-sa1100.c, 1.5, Dominik Brodowski
2004-08-30 12:19 ` Bruno Ducrot
2004-08-30 13:17   ` Dominik Brodowski
2004-08-30 14:49     ` Bruno Ducrot
2004-08-30 15:01       ` Dominik Brodowski
2004-08-30 15:16         ` Bruno Ducrot
2004-08-30 16:03           ` Dominik Brodowski
2004-08-30 14:29 ` Russell King
2004-08-30 15:08   ` Dominik Brodowski
2004-08-30 16:16     ` Russell King
2004-08-31 22:23       ` Dave Jones [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=20040831222358.GA19600@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    /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