From 6655e5828aa1e7c3ef0365eaf9bb8b196a39fb19 Mon Sep 17 00:00:00 2001 From: Andrew Morton Date: Sat, 22 Mar 2014 12:33:34 +1100 Subject: [PATCH] kmod-run-usermodehelpers-only-on-cpus-allowed-for-kthreadd-v2-checkpatch-fixes WARNING: line over 80 characters #67: FILE: kernel/kmod.c:214: + * Kthreadd can be restricted to a set of processors if the user wants to WARNING: line over 80 characters #69: FILE: kernel/kmod.c:216: + * we do not want to disturb the other processors here either so we start WARNING: line over 80 characters #70: FILE: kernel/kmod.c:217: + * the usermode helper threads only on the processors allowed for kthreadd. total: 0 errors, 3 warnings, 44 lines checked ./patches/kmod-run-usermodehelpers-only-on-cpus-allowed-for-kthreadd-v2.patch has style problems, please review. If any of these errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS. Please run checkpatch prior to sending patches Cc: Christoph Lameter Signed-off-by: Andrew Morton --- kernel/kmod.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/kernel/kmod.c b/kernel/kmod.c index 922f3d7c121149..55a36537fef4ac 100644 --- a/kernel/kmod.c +++ b/kernel/kmod.c @@ -211,10 +211,11 @@ static int ____call_usermodehelper(void *data) spin_unlock_irq(¤t->sighand->siglock); /* - * Kthreadd can be restricted to a set of processors if the user wants to - * protect other processors from OS latencies. If that has happened then - * we do not want to disturb the other processors here either so we start - * the usermode helper threads only on the processors allowed for kthreadd. + * Kthreadd can be restricted to a set of processors if the user wants + * to protect other processors from OS latencies. If that has happened + * then we do not want to disturb the other processors here either so we + * start the usermode helper threads only on the processors allowed for + * kthreadd. */ set_kthreadd_affinity();