cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Gary Hade <garyhade@us.ibm.com>
Cc: cpufreq@lists.linux.org.uk,
	Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: [PATCH] speedstep-centrino should ignore upper performance control bits
Date: Wed, 8 Nov 2006 19:22:08 -0500	[thread overview]
Message-ID: <20061109002208.GA805@redhat.com> (raw)
In-Reply-To: <20061109000031.GD28012@us.ibm.com>

On Wed, Nov 08, 2006 at 04:00:31PM -0800, Gary Hade wrote:

 > > Argh. I sat on the fence on this one until the dest settled,
 > > and now, as soon as I merge it, this happens. Bah!
 > Dave, I'm sorry.  I just discovered the problem. :(

Ok, I just tried to reconstruct my git tree without that diff
and hit problems trying to get the older patches applying against
a current tree, so I don't want to go down the route of making
everyone rediff and resend the 20 or so patches already queued.
However..

 > > Send an incremental against cpufreq.git so I don't have to
 > > reconstruct the whole git tree?  
 > Okay, I'll try to figure out how to do that.

git revert has nuked the change, but leaves a mess in the commits,
but I think we can live with that.  So just send the right fix,
and we'll make like this never happened :-)

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-11-09  0:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 23:39 [PATCH] speedstep-centrino should ignore upper performance control bits Gary Hade
2006-11-07  2:14 ` Dominik Brodowski
2006-11-07  7:09   ` Len Brown
2006-11-07 18:49     ` Gary Hade
2006-11-08 23:21       ` Gary Hade
2006-11-08 23:29         ` Dave Jones
2006-11-09  0:00           ` Gary Hade
2006-11-09  0:22             ` Dave Jones [this message]
2006-11-10 19:20               ` Gary Hade
2006-11-07 18:57 ` Gary Hade

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=20061109002208.GA805@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=garyhade@us.ibm.com \
    --cc=linux@dominikbrodowski.net \
    /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