From: Nigel Cunningham <nigel@tuxonice.net>
To: Dave Airlie <airlied@gmail.com>
Cc: Dave Airlie <airlied@linux.ie>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [BUG][PATCH] 2.6.36-rc showstopper (at least for me) in vmwgfx
Date: Tue, 05 Oct 2010 13:00:58 +1100 [thread overview]
Message-ID: <4CAA86DA.3080601@tuxonice.net> (raw)
In-Reply-To: <AANLkTikzSQuBOWR=Bf_3xuS+ioyvZ3LLXGuRnN-CHj7p@mail.gmail.com>
Hi.
On 05/10/10 12:51, Dave Airlie wrote:
> On Tue, Oct 5, 2010 at 8:57 AM, Nigel Cunningham<nigel@tuxonice.net> wrote:
>> Running a kernel based on the Rafael's -next tree, under VMware, I get the following oops while booting:
>
> Should already be fixed in Linus tree by,
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f1a28ee238bddfa48c5233543926af65a4445bf6
Ah, great. Thanks!
Nigel
prev parent reply other threads:[~2010-10-05 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 22:57 [BUG][PATCH] 2.6.36-rc showstopper (at least for me) in vmwgfx Nigel Cunningham
2010-10-05 1:51 ` Dave Airlie
2010-10-05 2:00 ` Nigel Cunningham [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=4CAA86DA.3080601@tuxonice.net \
--to=nigel@tuxonice.net \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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