From: Tim Gardner <tcanonical@tpi.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Dave Airlie <airlied@redhat.com>,
jbarnes@virtuousgeek.org, eric@anholt.net,
Kees Cook <kees@canonical.com>,
linux-kernel@vger.kernel.org, Gordon Jin <gordon.jin@intel.com>
Subject: Re: i915 boot regression on Q35 chipset with 2.6.35-rc4
Date: Wed, 21 Jul 2010 16:22:22 +0200 [thread overview]
Message-ID: <4C47029E.8020803@mail.tpi.com> (raw)
In-Reply-To: <8u3s94$g0j0tc@orsmga002.jf.intel.com>
On 07/21/2010 03:37 PM, Chris Wilson wrote:
> On Wed, 21 Jul 2010 14:35:22 +0200, Tim Gardner<tcanonical@tpi.com> wrote:
>> What's up with this patch? I haven't received any comment, nor has it
>> appeared in your git repository.
>
> Dave hasn't taken it because it is a regression fix for i915 and the
> current procedure is for those to go through Eric's tree. Eric has been
> busy working on a new compiler for GLSL the last few weeks and has been
> applying patches in batches.
>
> The patch I am happy to ack, but since I introduced the regression
> [https://bugzilla.kernel.org/show_bug.cgi?id=16294], I'd rather have
> someone more familiar with the intricacies of G33/G35/Q35 review it.
>
> For what is worth:
> Acked-by: Chris Wilson<chris@chris-wilson.co.uk>
>
The events that reminded me to look up the status of this patch were the
i915 regression fixes that recently appeared in
git-commits-head@vger.kernel.org from Dave's tree (which appears to be
contrary to the current procedure mentioned above).
rtg
--
Tim Gardner tim.gardner@canonical.com
next prev parent reply other threads:[~2010-07-21 14:23 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 [this message]
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
-- 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=4C47029E.8020803@mail.tpi.com \
--to=tcanonical@tpi.com \
--cc=airlied@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=eric@anholt.net \
--cc=gordon.jin@intel.com \
--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