[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20180424212241.16013-1-wvw@google.com>
Date: Tue, 24 Apr 2018 14:22:38 -0700
From: Wei Wang <wvw@...gle.com>
To: unlisted-recipients:; (no To-header on input)
Cc: gregkh@...uxfoundation.org, wei.vince.wang@...il.com,
Wei Wang <wvw@...gle.com>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...e.de>, Crt Mori <cmo@...exis.com>,
Randy Dunlap <rdunlap@...radead.org>,
linux-kernel@...r.kernel.org
Subject: [PATCH] kernel.h: fix a typo in comment
From: Wei Wang <wvw@...gle.com>
Signed-off-by: Wei Wang <wvw@...gle.com>
---
include/linux/kernel.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/kernel.h b/include/linux/kernel.h
index 6a1eb0b0aad96..e37e40ff14bba 100644
--- a/include/linux/kernel.h
+++ b/include/linux/kernel.h
@@ -664,7 +664,7 @@ do { \
* your code. (Extra memory is used for special buffers that are
* allocated when trace_printk() is used.)
*
- * A little optization trick is done here. If there's only one
+ * A little optimization trick is done here. If there's only one
* argument, there's no need to scan the string for printf formats.
* The trace_puts() will suffice. But how can we take advantage of
* using trace_puts() when trace_printk() has only one argument?
--
2.17.0.484.g0c8726318c-goog
Powered by blists - more mailing lists