public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: "Jin, Gordon" <gordon.jin@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
	"tim.gardner@canonical.com" <tim.gardner@canonical.com>,
	Dave Airlie <airlied@redhat.com>,
	"jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>,
	"eric@anholt.net" <eric@anholt.net>,
	Kees Cook <kees@canonical.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Hao, Xudong" <xudong.hao@intel.com>
Subject: Re: i915 boot regression on Q35 chipset with 2.6.35-rc4
Date: Thu, 22 Jul 2010 15:57:21 +0200	[thread overview]
Message-ID: <4C484E41.50606@gmail.com> (raw)
In-Reply-To: <B32E3D5F1713054290B4FF257B89C51A1F1DAA512D@shsmsx502.ccr.corp.intel.com>

On 07/22/2010 11:19 AM, Jin, Gordon wrote:
> Chris Wilson wrote on Wednesday, July 21, 2010 9:37 PM:
>> 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>
> 
> This patch fixes the bug on our G33 (0x29b2).

FWIW works for me too.

And as this is present as of 35-rc1 upstream, this means almost 2 months
lag since the break till now. Could you guys sort this up ASAP, please?

thanks,
-- 
js

  reply	other threads:[~2010-07-22 13:57 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 [this message]
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=4C484E41.50606@gmail.com \
    --to=jirislaby@gmail.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 \
    --cc=xudong.hao@intel.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