From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: [pull] drm-intel-fixes for 3.4
Date: Thu, 26 Apr 2012 17:35:01 +0200 [thread overview]
Message-ID: <20120426153501.GC5156@phenom.ffwll.local> (raw)
Hi Dave,
Nothing major here and imo can wait a bit if you don't have anything
important in drm-fixes yet:
- VGA load-detect fix. This bug seems to be as old as the load-detect code
(2.6.30), but needs stupid userspace (upowerd trying to detect
connectors on dpms-off outputs) to actually kill the machine. And
obviously a machine without VGA-hotplug, otherwise we don't do load
detect.
- 2 interger overflow fixes for unpriviledged ioctls from Xi Wang.
Yours, Daniel
The following changes since commit 66f75a5d028beaf67c931435fdc3e7823125730c:
Linux 3.4-rc4 (2012-04-21 14:47:52 -0700)
are available in the git repository at:
git://people.freedesktop.org/~danvet/drm-intel drm-intel-fixes
for you to fetch changes up to 44afb3a04391a74309d16180d1e4f8386fdfa745:
drm/i915: fix integer overflow in i915_gem_do_execbuffer() (2012-04-23 22:32:15 +0200)
----------------------------------------------------------------
Daniel Vetter (1):
drm/i915: fixup load-detect on enabled, but not active pipe
Xi Wang (2):
drm/i915: fix integer overflow in i915_gem_execbuffer2()
drm/i915: fix integer overflow in i915_gem_do_execbuffer()
drivers/gpu/drm/i915/i915_gem_execbuffer.c | 8 +++++++-
drivers/gpu/drm/i915/intel_crt.c | 29 +++++++++++-----------------
2 files changed, 18 insertions(+), 19 deletions(-)
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next reply other threads:[~2012-04-26 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 15:35 Daniel Vetter [this message]
2012-04-26 17:00 ` [pull] drm-intel-fixes for 3.4 Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2012-04-03 14:56 Daniel Vetter
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=20120426153501.GC5156@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox