aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/trace-event-scripting.c
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <[email protected]>2014-04-07 12:49:36 -0700
committerGreg Kroah-Hartman <[email protected]>2014-04-07 12:49:36 -0700
commit806192c07d889ab4821e396793bbcc4c7f2fad94 (patch)
tree4a13c9a56daf359bdbda917ad34ab69dcada4d2a /tools/perf/util/trace-event-scripting.c
parentb0e2796029d26f4541e9cb1e9f54e1a7020618c6 (diff)
Staging: unisys: mark drivers as BROKEN
Turns out these drivers like to mess around with the system even if the hardware they control isn't present. That's not good, and people are starting to report lots of issues with this in their build/boot testing. So for now, let's just mark them as BROKEN, until the code gets converted to use the proper driver model interaction (i.e. don't do anything until the hardware is actually found in the system.) Reported-by: Fengguang Wu <[email protected]> Reported-by: Sasha Levin <[email protected]> Cc: Benjamin Romer <[email protected]> Cc: David Kershner <[email protected]> Cc: someone <[email protected]> Cc: Ken Cox <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions