__local_bh_disable_ip() is neither for strict internal use nor does it require the caller to disable hardirqs. Probaby a celebration for ancient behaviour.
Reviewed-by: David S. Miller <[email protected]> Signed-off-by: Frederic Weisbecker <[email protected]> Cc: Mauro Carvalho Chehab <[email protected]> Cc: Joel Fernandes <[email protected]> Cc: Thomas Gleixner <[email protected]> Cc: Pavan Kondeti <[email protected]> Cc: Paul E . McKenney <[email protected]> Cc: David S . Miller <[email protected]> Cc: Ingo Molnar <[email protected]> Cc: Sebastian Andrzej Siewior <[email protected]> Cc: Linus Torvalds <[email protected]> Cc: Peter Zijlstra <[email protected]> --- kernel/softirq.c | 4 ---- 1 file changed, 4 deletions(-) diff --git a/kernel/softirq.c b/kernel/softirq.c index 6c703bbb718b..60d1706ad47e 100644 --- a/kernel/softirq.c +++ b/kernel/softirq.c @@ -104,10 +104,6 @@ static bool ksoftirqd_running(unsigned long pending) * softirq and whether we just have bh disabled. */ -/* - * This one is for softirq.c-internal use, - * where hardirqs are disabled legitimately: - */ #ifdef CONFIG_TRACE_IRQFLAGS void __local_bh_disable_ip(unsigned long ip, unsigned int cnt) { -- 2.21.0
