From: Greg KH <greg@kroah.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@kernel.org, lwn@lwn.net
Subject: Re: Linux 2.6.36.1
Date: Tue, 7 Dec 2010 12:20:18 -0800 [thread overview]
Message-ID: <20101207202018.GB11264@kroah.com> (raw)
In-Reply-To: <201011231343.21778.Martin@lichtvoll.de>
On Tue, Nov 23, 2010 at 01:43:09PM +0100, Martin Steigerwald wrote:
> Am Montag 22 November 2010 schrieb Greg KH:
> > I'm announcing the release of the 2.6.36.1 kernel.
> >
> > All users of the 2.6.36 kernel series must upgrade.
> >
> > The updated 2.6.36.y git tree can be found at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.36.y.gi
> > t and can be browsed at the normal kernel.org git web browser:
> >
> > http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.36.y.git;a=
> > summary
>
> I am missing
>
> drm/radeon/kms: MC vram map needs to be >= pci aperture size
> b7d8cce5b558e0c0aa6898c9865356481598b46d
>
> from Alex Deucher which fixes
>
> Bug 28402 - random radeon/kms/drm related freezes with kernel 2.6.34
> https://bugs.freedesktop.org/show_bug.cgi?id=28402
>
> random - possibly Radeon DRM KMS related - freezes
> https://bugzilla.kernel.org/show_bug.cgi?id=16376
>
> which according should have been queued for stable[1]
>
> [1] https://bugs.freedesktop.org/show_bug.cgi?id=28402#c96
It's now in this next release.
thanks,
greg k-h
next prev parent reply other threads:[~2010-12-07 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 19:18 Linux 2.6.36.1 Greg KH
2010-11-22 19:18 ` Greg KH
2010-11-22 20:52 ` Felipe Contreras
2010-11-22 21:32 ` Greg KH
2010-11-22 23:55 ` Dave Jones
2010-12-07 20:21 ` Greg KH
2010-11-23 12:43 ` Martin Steigerwald
2010-12-07 20:20 ` Greg KH [this message]
2010-11-24 14:19 ` Mario 'BitKoenig' Holbe
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=20101207202018.GB11264@kroah.com \
--to=greg@kroah.com \
--cc=Martin@lichtvoll.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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