All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Dave Airlie <airlied@linux.ie>
Cc: intel-gfx@lists.freedesktop.org
Subject: [git pull] i915 fixes
Date: Tue, 01 Mar 2011 23:56:12 +0000	[thread overview]
Message-ID: <1bdc18$jo41au@fmsmga002.fm.intel.com> (raw)

As I don't anticipate any more fixes in the near future for 2.6.38, I
thought I may as well send this single patch to prevent 965G[M] from
using a status page above 4GiB, in a timely fashion.
-Chris

The following changes since commit dd9c1549edef02290edced639f67b54a25abbe0e:

  Linux 2.6.38-rc7 (2011-03-01 13:55:12 -0800)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git drm-intel-fixes

Jan Niehusmann (1):
      drm/i915: fix memory corruption with GM965 and >4GB RAM

 drivers/gpu/drm/i915/i915_dma.c |   11 +++++++++++
 1 files changed, 11 insertions(+), 0 deletions(-)

-- 
Chris Wilson, Intel Open Source Technology Centre

             reply	other threads:[~2011-03-01 23:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01 23:56 Chris Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-07 12:00 [git pull] i915 fixes Chris Wilson
2011-03-07 21:28 ` Jim Gettys
2011-03-08  4:00   ` Dave Airlie
2011-03-08 19:47     ` Jesse Barnes
2011-03-08  4:08   ` Jim Gettys
2011-03-08  7:27     ` Dave Airlie
2011-03-08  8:32       ` Chris Wilson
2011-02-24  1:09 Chris Wilson
2011-02-24 15:06 ` Jesse Barnes
2011-02-11  9:58 Chris Wilson
2011-02-12  2:04 ` Eric Anholt
2011-02-12 18:35   ` Chris Wilson
2011-02-01  9:44 Chris Wilson
2010-12-30 19:01 Chris Wilson
2010-12-30 22:01 ` Jesse Barnes
2010-12-30 22:18   ` Chris Wilson
2010-12-30 22:29   ` Linus Torvalds
2010-12-30 22:53     ` Chris Wilson

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='1bdc18$jo41au@fmsmga002.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=airlied@linux.ie \
    --cc=intel-gfx@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.