From: Stefan Bader <stefan.bader@canonical.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>,
"stable@kernel.org" <stable@kernel.org>
Subject: [ANNOUNCE] linux-2.6.32.y-drm33.z
Date: Thu, 29 Apr 2010 10:23:45 +0100 [thread overview]
Message-ID: <4BD95021.7010306@canonical.com> (raw)
As many of us now have a distribution which is based on a 2.6.32 kernel but are
forced to update DRM to the version in 2.6.33 to obtain good graphics
experience. In support of this I went ahead and created a tree on kernel.org[1]
which brings together the two and which I will maintain following the upstream
stable trees from Greg. This hopefully will not only be beneficial to us but
also to all that are in the need of running this combination of code.
-Stefan
[1] http://git.kernel.org/?p=linux/kernel/git/smb/linux-2.6.32.y-drm33.z.git
next reply other threads:[~2010-05-01 1:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 9:23 Stefan Bader [this message]
2010-04-29 17:12 ` [ANNOUNCE] linux-2.6.32.y-drm33.z Luis R. Rodriguez
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=4BD95021.7010306@canonical.com \
--to=stefan.bader@canonical.com \
--cc=kernel-team@lists.ubuntu.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