From: Andy Whitcroft <apw@canonical.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Woody Suwalski <woodys@xandros.com>,
jbarnes@virtuousgeek.org, eric@anholt.net,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, stable@kernel.org,
tim.gardner@canonical.com, stefan.bader@canonical.com
Subject: Re: Intel 915GM MCHBAR bug
Date: Sat, 6 Jun 2009 23:58:02 +0100 [thread overview]
Message-ID: <20090606225802.GL10751@shadowen.org> (raw)
In-Reply-To: <4A2A0E8C.1010109@cs.helsinki.fi>
On Sat, Jun 06, 2009 at 09:37:00AM +0300, Pekka Enberg wrote:
> Hi Andrew,
>
> On Sat, 06 Jun 2009 09:14:41 +0300 Pekka Enberg <penberg@cs.helsinki.fi>
> wrote:
>>>>> Wanna show us the patch?
>>>>>
>>>>> Because the world could certainly do with more i915 bugfixes :(
>>>> Here is Jesse's patch from
>>>> http://lists.freedesktop.org/archives/intel-gfx/2009-January/001186.html
>>>> adopted for 2.6.30-rc8... (needed to redo hunk #3 for
>>>> i915_gem_tile.c)
>>> Yup. I took the two patches from here:
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/349314
>>>
>>> and did the same rediffing on top of 2.6.30-rc8 for the first one.
>>>
>>> Andrew, do you want me to forward you the (tested) patches or should
>>> we wait for Jesse et al to take care of it?
>>
>> Yes, please send them out.
>
> OK, I did that. I am bit unhappy that I had to do it, though. The patch
> dates back to January (!) and Ubuntu folks have been carrying it for a
> while now.
We cirtainly have been carrying for some time. My understanding was
that the maintainers had it and had been expecting it to merge through
them. Did we miss a trick somewhere?
-apw
prev parent reply other threads:[~2009-06-06 22:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A242C81.6020906@cs.helsinki.fi>
[not found] ` <20090604112738.4c01d35e@jbarnes-x200>
2009-06-05 8:02 ` Intel 915GM MCHBAR bug Pekka Enberg
2009-06-05 20:00 ` Andrew Morton
2009-06-05 21:09 ` Woody Suwalski
2009-06-06 6:14 ` Pekka Enberg
2009-06-06 6:27 ` Andrew Morton
2009-06-06 6:37 ` Pekka Enberg
2009-06-06 20:27 ` Jesse Barnes
2009-06-09 22:07 ` [Intel-gfx] " Jesse Barnes
2009-06-09 22:28 ` Andrew Morton
2009-06-29 17:33 ` [stable] " Greg KH
2009-06-29 18:27 ` Greg KH
2009-06-29 18:51 ` Ozan Çağlayan
2009-06-29 20:45 ` Greg KH
2009-06-06 22:58 ` Andy Whitcroft [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=20090606225802.GL10751@shadowen.org \
--to=apw@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=stable@kernel.org \
--cc=stefan.bader@canonical.com \
--cc=tim.gardner@canonical.com \
--cc=torvalds@linux-foundation.org \
--cc=woodys@xandros.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