From: Dave Airlie <airlied@redhat.com>
To: tim.gardner@canonical.com
Cc: chris@chris-wilson.co.uk, jbarnes@virtuousgeek.org,
eric@anholt.net, Kees Cook <kees@canonical.com>,
linux-kernel@vger.kernel.org
Subject: re: i915 boot regression on Q35 chipset with 2.6.35-rc4
Date: Thu, 22 Jul 2010 06:30:05 +1000 [thread overview]
Message-ID: <1279744205.4042.0.camel@t60prh> (raw)
In-Reply-To: <4C46E98A.3010206@mail.tpi.com>
On Wed, 2010-07-21 at 14:35 +0200, Tim Gardner wrote:
> Dave,
>
> http://lkml.org/lkml/2010/7/9/287
>
> What's up with this patch? I haven't received any comment, nor has it
> appeared in your git repository.
I don't deal with Intel patches directly, Eric?
Dave.
next prev parent reply other threads:[~2010-07-21 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 12:35 i915 boot regression on Q35 chipset with 2.6.35-rc4 Tim Gardner
2010-07-21 13:37 ` Chris Wilson
2010-07-21 14:22 ` Tim Gardner
2010-07-22 9:19 ` Jin, Gordon
2010-07-22 13:57 ` Jiri Slaby
2010-07-22 23:59 ` Jin, Gordon
2010-07-21 20:30 ` Dave Airlie [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-09 20:48 Tim Gardner
2010-07-09 23:52 ` Woody Suwalski
2010-07-26 18:23 ` Eric Anholt
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=1279744205.4042.0.camel@t60prh \
--to=airlied@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--cc=kees@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.gardner@canonical.com \
/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