All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Thomas Renninger <trenn@suse.de>
Cc: Dave Jones <davej@codemonkey.org.uk>, Greg KH <gregkh@suse.de>,
	Stable <Stable@kernel.org>,
	cpufreq@lists.linux.org.uk
Subject: Re: [stable] [PATCH] Make acpi-cpufreq more robust against BIOS freq changes behind our back
Date: Wed, 21 May 2008 08:00:41 -0700	[thread overview]
Message-ID: <20080521150041.GA15975@kroah.com> (raw)
In-Reply-To: <1211375701.29901.11.camel@queen.suse.de>

On Wed, May 21, 2008 at 03:15:01PM +0200, Thomas Renninger wrote:
> On Wed, 2008-05-21 at 15:08 +0200, Thomas Renninger wrote:
> > Hi,
> > 
> > Please consider this one for stable integration.
> ...
> > If this one patches for you for 2.6.24.4 also, maybe it even gets in
> > there.
> Hmm, I added this to OpenSUSE 10.3, means 2.6.22.
> I only had to adjust the arch/i386 vs arch/x86 patch.
> If this gets into the stable kernel, I wonder how far back this makes
> sense. Shall I send a 2.6.22 based version?

The stable team is only tracking 2.6.25 kernels right now, anything
older than that is not something we currently care about.

thanks,

greg k-h

  reply	other threads:[~2008-05-21 15:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 18:15 acpi_cpufreq stepping issue on Pentium M 1.2GHz Anthony L. Awtrey
2008-05-19  0:08 ` Dave Jones
2008-05-19 11:29   ` Anthony L. Awtrey
2008-05-19 13:14     ` Dave Jones
2008-05-19 13:38       ` Anthony L. Awtrey
2008-05-20 10:38   ` Thomas Renninger
2008-05-21 12:51     ` Anthony L. Awtrey
2008-05-21 13:08       ` [PATCH] Make acpi-cpufreq more robust against BIOS freq changes behind our back Thomas Renninger
2008-05-21 13:15         ` Thomas Renninger
2008-05-21 15:00           ` Greg KH [this message]
2008-05-21 18:48           ` Anthony L. Awtrey
2008-05-23  9:20             ` Thomas Renninger
2008-05-21 15:46         ` Anthony L. Awtrey
2008-06-02 22:36           ` [stable] " Chris Wright
2008-06-11 14:33             ` Thomas Renninger

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=20080521150041.GA15975@kroah.com \
    --to=greg@kroah.com \
    --cc=Stable@kernel.org \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=gregkh@suse.de \
    --cc=trenn@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.