public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: Jerome Glisse <glisse@freedesktop.org>
Cc: Greg KH <greg@kroah.com>,
	stable@kernel.org, Alex Deucher <alexdeucher@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [stable]  please consider drm radeon kms agp release
Date: Mon, 31 May 2010 23:56:26 +0200	[thread overview]
Message-ID: <201005312356.27299.Martin@lichtvoll.de> (raw)
In-Reply-To: <20100531193815.GD2413@barney.localdomain>

[-- Attachment #1: Type: Text/Plain, Size: 1045 bytes --]

Am Montag 31 Mai 2010 schrieb Jerome Glisse:
> On Mon, May 31, 2010 at 10:02:34AM -0700, Greg KH wrote:
> > On Mon, May 31, 2010 at 04:42:41PM +0200, Martin Steigerwald wrote:
> > > Hi Greg, hi stable kernel team,
> > > 
> > > Please consider the attached patch from Jérôme Glisse. It fixes drm
> > > radeon KMS after coming out from a snapshot cycle [1] - no matter
> > > whether I use userspace software suspend or TuxOnIce.
> > > 
> > > Verified on my notebook ThinkPad T42 and by cedric, the reporter of
> > > above bug.
> > 
> > Which stable kernel release do you want to see this patch in?  .27,
> > .32, .33, or .34?  Yeah, there's a lot active at the moment :(
> > 
> > thanks,
> > 
> > greg k-h
> 
> 2.6.34 sorry if i wasn't clear when ccing stable while sending patch
> for 2.6.35.

Yeah forgot to mention it also, in 2.6.33 it works. In 2.6.35 its fixed. So 
it applies for 2.6.34.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-05-31 21:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31 14:42 [stable] please consider drm radeon kms agp release Martin Steigerwald
2010-05-31 17:02 ` Greg KH
2010-05-31 19:38   ` Jerome Glisse
2010-05-31 21:56     ` Martin Steigerwald [this message]
2010-06-23 20:28       ` Greg KH

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=201005312356.27299.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=alexdeucher@gmail.com \
    --cc=glisse@freedesktop.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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