aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <[email protected]>2019-07-03 09:16:53 +0200
committerGreg Kroah-Hartman <[email protected]>2019-07-03 16:55:51 +0200
commit43e23b6c0b0151e308acbd6530bb80e2d2e53161 (patch)
tree0a075e6ff4dfd069c047f55d47c0e691cfacdfea /tools/perf/util/scripting-engines/trace-event-python.c
parentfb59b7824da884e042f44dad9c713f221ded93c9 (diff)
debugfs: log errors when something goes wrong
As it is not recommended that debugfs calls be checked, it was pointed out that major errors should still be logged somewhere so that developers and users have a chance to figure out what went wrong. To help with this, error logging has been added to the debugfs core so that it is not needed to be present in every individual file that calls debugfs. Reported-by: Mark Brown <[email protected]> Reported-by: Takashi Iwai <[email protected]> Reviewed-by: Mark Brown <[email protected]> Reviewed-by: Takashi Iwai <[email protected]> Reviewed-by: Rafael J. Wysocki <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions