summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2017-06-20 02:37:26 +0300
committerThomas Gleixner <tglx@linutronix.de>2017-06-22 19:21:16 +0300
commit735c09524d3e7c92315e8e2699a1b9acb4fb415c (patch)
treee2ca5ba2a741242fd9ac05a3a0155783a9e887a6 /tools/perf/scripts/python/call-graph-from-postgresql.py
parent0dd945ff4647a1f29c6ae8f4f9a69c8f37c994cf (diff)
downloadlinux-735c09524d3e7c92315e8e2699a1b9acb4fb415c.tar.xz
genirq/cpuhotplug: Dont claim success on error
In case the affinity of an interrupt was broken, a printk is emitted. But if the affinity cannot be set at all due to a missing irq_set_affinity() callback or due to a failing callback, the message is still printed preceeded by a warning/error. That makes no sense whatsoever. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: Jens Axboe <axboe@kernel.dk> Cc: Marc Zyngier <marc.zyngier@arm.com> Cc: Michael Ellerman <mpe@ellerman.id.au> Cc: Keith Busch <keith.busch@intel.com> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Christoph Hellwig <hch@lst.de> Link: http://lkml.kernel.org/r/20170619235445.274852976@linutronix.de
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions