vsprintf-kptr_restrict-is-okay-in-irq-when-2-checkpatch-fixes

WARNING: line over 80 characters
#46: FILE: lib/vsprintf.c:1674:
+			 * kptr_restrict==1 cannot be used in IRQ context because

total: 0 errors, 1 warnings, 43 lines checked

./patches/vsprintf-kptr_restrict-is-okay-in-irq-when-2.patch has style problems, please review.

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.

Please run checkpatch prior to sending patches

Cc: Jason A. Donenfeld <Jason@zx2c4.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

diff --git a/lib/vsprintf.c b/lib/vsprintf.c
index 881c398d5dda7a84eae1bf5c5beb0d0990f1070c..f44e178e6edec22e2f7c405f8cb433b2be935f83 100644 (file)
--- a/lib/vsprintf.c
+++ b/lib/vsprintf.c
@@ -1598,8 +1598,8 @@ char *pointer(const char *fmt, char *buf, char *end, void *ptr,
                        const struct cred *cred;
 
                        /*
-                        * kptr_restrict==1 cannot be used in IRQ context because
-                        * its test for CAP_SYSLOG would be meaningless.
+                        * kptr_restrict==1 cannot be used in IRQ context
+                        * because its test for CAP_SYSLOG would be meaningless.
                         */
                        if (in_irq() || in_serving_softirq() || in_nmi()) {
                                if (spec.field_width == -1)