summaryrefslogtreecommitdiff
path: root/reference/C/EXAMPLES/enum2.c
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2009-01-03 19:07:45 +0100
committerTobias Klauser <tklauser@distanz.ch>2009-01-03 19:07:45 +0100
commit62b161ba323e9dc2669e1e9b090f22efcc6ced48 (patch)
treecc767bb4790890250708d4f6471a072271fee867 /reference/C/EXAMPLES/enum2.c
parent149ca2f7c91b55671732f76825be7f275bfcacbd (diff)
Packaging updates
* Replaced obsolete dh_clean -k with dh_prep in rules. * Update debhelper compatibility level to 7. * Changed maintainer email address.
Diffstat (limited to 'reference/C/EXAMPLES/enum2.c')
0 files changed, 0 insertions, 0 deletions
58/0x140 [i915] process_one_work+0x1f1/0x480 worker_thread+0x48/0x4d0 kthread+0x101/0x140 and this patch purely papers over the issue by adding a NULL pointer check and a WARN_ON_ONCE() to avoid the oops that would then generally make the machine unresponsive. Other callers of i915_gem_object_to_ggtt() seem to also check for the returned pointer being NULL and warn about it, so this clearly has happened before in other places. [ Reported it originally to the i915 developers on Jan 8, applying the ugly workaround on my own now after triggering the problem for the second time with no feedback. This is likely to be the same bug reported as https://bugs.freedesktop.org/show_bug.cgi?id=98829 https://bugs.freedesktop.org/show_bug.cgi?id=99134 which has a patch for the underlying problem, but it hasn't gotten to me, so I'm applying the workaround. ] Cc: Daniel Vetter <daniel.vetter@intel.com> Cc: Jani Nikula <jani.nikula@linux.intel.com> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com> Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Cc: Imre Deak <imre.deak@intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation')