mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Len Brown <lenb@kernel.org>
Cc: stable@kernel.org, linux-pm@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [stable] [linux-pm] [git pull 2.6.36.stable] intel_idle patches for 2.6.36.stable
Date: Mon, 22 Nov 2010 10:45:59 -0800	[thread overview]
Message-ID: <20101122184559.GA10879@kroah.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1011221318230.19247@x980>

On Mon, Nov 22, 2010 at 01:36:31PM -0500, Len Brown wrote:
> Hi Greg,
> 
> I retract my intel_idle pull requests for .stable
> 
> The idle-release branches in...
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/
> 	linux-idle-2.6.32.git
> 	linux-idle-2.6.35.git
> 	linux-idle-2.6.36.git
> 
> are for distros and others that want to run the latest intel_idle
> driver on the specified release.  The backports in these trees
> contain every upstream patch that touch the driver, including new
> platform support and any dependent cosmetic patches.
> 
> So they are optimized for the maintenance task of comparing
> the backport versus the upstream driver to verify the release
> includes everything that is upstream.
> However, as it does not exclude cosmetic or trivial patches,
> the backports do not qualify for inclusion in .stable.
> 
> Sorry to bother you.

No problem at all, glad to see you change your mind :)

thanks,

greg k-h

      reply	other threads:[~2010-11-22 18:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 17:29 Len Brown
2010-11-15 18:49 ` [stable] " Greg KH
2010-11-17  7:06   ` Len Brown
2010-11-17  7:44   ` Len Brown
2010-11-17  8:28 ` Len Brown
2010-11-17  8:33   ` Len Brown
2010-11-22 18:36     ` [linux-pm] " Len Brown
2010-11-22 18:45       ` Greg KH [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=20101122184559.GA10879@kroah.com \
    --to=greg@kroah.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=stable@kernel.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

Powered by JetHome