From: Knut Petersen <Knut_Petersen@t-online.de>
To: Keith Packard <keithp@keithp.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [BUG][2.6.39-rc7]
Date: Tue, 17 May 2011 00:53:38 +0200 [thread overview]
Message-ID: <4DD1AAF2.7030502@t-online.de> (raw)
In-Reply-To: <yunei3y1g9u.fsf@aiko.keithp.com>
> The fix for this bug is still under review and was not ready in time for
> 2.6.39. It is planned for merging in the 2.6.40 time frame, and should
> be suitable for a stable backport when merged to master.
>
Nice to know that .39 will have the feature to lock screen and all input devices
on exotic hardware like i915GM.
Well, .31 and Xorg 1.6.5 are still around and good enough for months of uptime.
cu,
Knut
next prev parent reply other threads:[~2011-05-16 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 7:39 [BUG][2.6.39-rc7] Knut Petersen
2011-05-16 21:34 ` [BUG][2.6.39-rc7] Keith Packard
2011-05-16 22:53 ` Knut Petersen [this message]
2011-05-17 4:18 ` [BUG][2.6.39-rc7] Keith Packard
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=4DD1AAF2.7030502@t-online.de \
--to=knut_petersen@t-online.de \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.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