From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
intel-gfx@lists.freedesktop.org, woodys@xandros.com,
stefan.bader@canonical.com, linux-kernel@vger.kernel.org,
penberg@cs.helsinki.fi, Jesse Barnes <jbarnes@virtuousgeek.org>,
apw@canonical.com, tim.gardner@canonical.com,
torvalds@linux-foundation.org, stable@kernel.org
Subject: Re: [stable] [Intel-gfx] Intel 915GM MCHBAR bug
Date: Mon, 29 Jun 2009 21:51:51 +0300 [thread overview]
Message-ID: <4A490D47.7030305@pardus.org.tr> (raw)
In-Reply-To: <20090629182738.GD3901@kroah.com>
Greg KH wrote:
> I take it back. It doesn't build properly on 2.6.30, can someone
> backport commit d765898970f35acef960581f678b9da9d5c779fa to the 2.6.30
> tree and send it to stable@kernel.org so that we can apply it to resolve
> this issue?
> ease read the FAQ at http://www.tux.org/lkml/
>
There was this commit on top of them which was fixed the build problem
for me:
http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fanholt%2Fdrm-intel.git;a=commitdiff_plain;h=34c8638bb5ee130b8151c57708284bcd4972e2e1;hp=003c9ca68810bc0a63a1f3ff6beec839b197e23b
next prev parent reply other threads:[~2009-06-29 19:00 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 [this message]
2009-06-29 20:45 ` Greg KH
2009-06-06 22:58 ` Andy Whitcroft
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=4A490D47.7030305@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=greg@kroah.com \
--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