aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorChris Wilson <[email protected]>2012-01-29 16:45:32 +0000
committerDave Airlie <[email protected]>2012-01-30 09:31:42 +0000
commitdd8bc93d45c0ac4f64bf074d4be72418aac1609b (patch)
tree79bc34bf0a99619b99a505642d39b38f354742e0 /tools/perf/util/scripting-engines/trace-event-python.c
parent6e877b576ddf7cde5db2e9a6dcb56fef0ea77e64 (diff)
drm: Pass the real error code back during GEM bo initialisation
In particular, I found I was hitting the max-file limit in the VFS, and the EFILE was being magically transformed into ENOMEM. Confusion reigns. Signed-off-by: Chris Wilson <[email protected]> Reviewed-by: Daniel Vetter <[email protected]> Signed-off-by: Dave Airlie <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions