aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorSuresh Jayaraman <[email protected]>2011-09-21 10:00:16 +0200
committerJens Axboe <[email protected]>2011-09-21 10:00:16 +0200
commit75df713627f28f88b901b329c8857747545fd4ab (patch)
tree0986bc4d82595dae4a3fabb15fce4780c053f004 /tools/perf/util/scripting-engines/trace-event-python.c
parent27a84d54c02591e815d291ae0ee4bfb9cfd21065 (diff)
block: document blk-plug
Thus spake Andrew Morton: "And I have the usual maintainability whine. If someone comes up to vmscan.c and sees it calling blk_start_plug(), how are they supposed to work out why that call is there? They go look at the blk_start_plug() definition and it is undocumented. I think we can do better than this?" Adapted from the LWN article - http://lwn.net/Articles/438256/ by Jens Axboe and from an earlier attempt by Shaohua Li to document blk-plug. [[email protected]: grammatical and spelling tweaks] Signed-off-by: Suresh Jayaraman <[email protected]> Cc: Shaohua Li <[email protected]> Cc: Jonathan Corbet <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions