Skip to contentSkip to conversation

linux/kernel.h: Fix minor type in comment

PATCH In review Yuval Shaia 2 participants 3 messages Apr 10, 2018

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 linux/kernel.h: Fix minor type in comment

---
 include/linux/kernel.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
include/linux/kernel.h +1 -1
index ce51455e2adf..a5b4ba3bdb61 100644
@@ -651,7 +651,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?
Signature · 1 line
2.14.3
#1 lore raw
Quoted 10 lines · Yuval Shaia
---
 include/linux/kernel.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
include/linux/kernel.h +0 -0
index ce51455e2adf..a5b4ba3bdb61 100644

include/linux/kernel.h do { \ · line 657

Quoted 8 lines
include/linux/kernel.h +1 -1
@@ -651,7 +651,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?

Please also fix the typo in the title ;-)

Thanks,

Ingo

#2 lore raw
Quoted 8 lines · Ingo Molnar
Quoted 5 lines · Yuval Shaia
---
 include/linux/kernel.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Quoted 15 lines

include/linux/kernel.h do { \ · line 657

Quoted 13 lines
include/linux/kernel.h +1 -1
index ce51455e2adf..a5b4ba3bdb61 100644
@@ -651,7 +651,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?

Please also fix the typo in the title ;-)

Sorry, fixed that but forgot to amend :)

Will post v2 in few seconds.

Quoted 4 lines

Thanks,

Ingo