aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/failed-syscalls-by-pid.py
diff options
context:
space:
mode:
authorTetsuo Handa <[email protected]>2019-02-22 18:59:40 +0900
committerPetr Mladek <[email protected]>2019-03-04 13:42:05 +0100
commite36202a844d4eff2ab07bcef998d7b4beda9761f (patch)
tree39134e023133895f7bed7973e7b8f0613e38b59f /tools/perf/scripts/python/failed-syscalls-by-pid.py
parentb60706644282af04e4aa57da5af57470d453cd1f (diff)
printk: Remove no longer used LOG_PREFIX.
When commit 5becfb1df5ac8e49 ("kmsg: merge continuation records while printing") introduced LOG_PREFIX, we used KERN_DEFAULT etc. as a flag for setting LOG_PREFIX in order to tell whether to call cont_add() (i.e. whether to append the message to "struct cont"). But since commit 4bcc595ccd80decb ("printk: reinstate KERN_CONT for printing continuation lines") inverted the behavior (i.e. don't append the message to "struct cont" unless KERN_CONT is specified) and commit 5aa068ea4082b39e ("printk: remove games with previous record flags") removed the last LOG_PREFIX check, setting LOG_PREFIX via KERN_DEFAULT etc. is no longer meaningful. Therefore, we can remove LOG_PREFIX and make KERN_DEFAULT empty string. Link: http://lkml.kernel.org/r/1550829580-9189-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp To: Steven Rostedt <[email protected]> To: Linus Torvalds <[email protected]> Cc: [email protected] Cc: Tetsuo Handa <[email protected]> Signed-off-by: Tetsuo Handa <[email protected]> Reviewed-by: Sergey Senozhatsky <[email protected]> Signed-off-by: Petr Mladek <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions