The patch titled
Subject: kernel: fix typos and some coding style in comments
has been removed from the -mm tree. Its filename was
kernel-fix-typos-and-some-coding-style-in-comments.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Weitao Hou <houweitaoo@xxxxxxxxx>
Subject: kernel: fix typos and some coding style in comments
fix lenght to length
Link: http://lkml.kernel.org/r/20190521050937.4370-1-houweitaoo@xxxxxxxxx
Signed-off-by: Weitao Hou <houweitaoo@xxxxxxxxx>
Acked-by: Kees Cook <keescook@xxxxxxxxxxxx>
Cc: Colin Ian King <colin.king@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
Documentation/devicetree/bindings/usb/s3c2410-usb.txt | 2 -
drivers/net/wireless/mediatek/mt76/mt76x02_usb_core.c | 2 -
kernel/sysctl.c | 18 +++++-----
sound/soc/qcom/qdsp6/q6asm.c | 2 -
4 files changed, 12 insertions(+), 12 deletions(-)
--- a/Documentation/devicetree/bindings/usb/s3c2410-usb.txt~kernel-fix-typos-and-some-coding-style-in-comments
+++ a/Documentation/devicetree/bindings/usb/s3c2410-usb.txt
@@ -4,7 +4,7 @@ OHCI
Required properties:
- compatible: should be "samsung,s3c2410-ohci" for USB host controller
- - reg: address and lenght of the controller memory mapped region
+ - reg: address and length of the controller memory mapped region
- interrupts: interrupt number for the USB OHCI controller
- clocks: Should reference the bus and host clocks
- clock-names: Should contain two strings
--- a/drivers/net/wireless/mediatek/mt76/mt76x02_usb_core.c~kernel-fix-typos-and-some-coding-style-in-comments
+++ a/drivers/net/wireless/mediatek/mt76/mt76x02_usb_core.c
@@ -53,7 +53,7 @@ int mt76x02u_skb_dma_info(struct sk_buff
pad = round_up(skb->len, 4) + 4 - skb->len;
/* First packet of a A-MSDU burst keeps track of the whole burst
- * length, need to update lenght of it and the last packet.
+ * length, need to update length of it and the last packet.
*/
skb_walk_frags(skb, iter) {
last = iter;
--- a/kernel/sysctl.c~kernel-fix-typos-and-some-coding-style-in-comments
+++ a/kernel/sysctl.c
@@ -188,17 +188,17 @@ extern int no_unaligned_warning;
* enum sysctl_writes_mode - supported sysctl write modes
*
* @SYSCTL_WRITES_LEGACY: each write syscall must fully contain the sysctl value
- * to be written, and multiple writes on the same sysctl file descriptor
- * will rewrite the sysctl value, regardless of file position. No warning
- * is issued when the initial position is not 0.
+ * to be written, and multiple writes on the same sysctl file descriptor
+ * will rewrite the sysctl value, regardless of file position. No warning
+ * is issued when the initial position is not 0.
* @SYSCTL_WRITES_WARN: same as above but warn when the initial file position is
- * not 0.
+ * not 0.
* @SYSCTL_WRITES_STRICT: writes to numeric sysctl entries must always be at
- * file position 0 and the value must be fully contained in the buffer
- * sent to the write syscall. If dealing with strings respect the file
- * position, but restrict this to the max length of the buffer, anything
- * passed the max lenght will be ignored. Multiple writes will append
- * to the buffer.
+ * file position 0 and the value must be fully contained in the buffer
+ * sent to the write syscall. If dealing with strings respect the file
+ * position, but restrict this to the max length of the buffer, anything
+ * passed the max length will be ignored. Multiple writes will append
+ * to the buffer.
*
* These write modes control how current file position affects the behavior of
* updating sysctl values through the proc interface on each write.
--- a/sound/soc/qcom/qdsp6/q6asm.c~kernel-fix-typos-and-some-coding-style-in-comments
+++ a/sound/soc/qcom/qdsp6/q6asm.c
@@ -1194,7 +1194,7 @@ EXPORT_SYMBOL_GPL(q6asm_open_read);
* q6asm_write_async() - non blocking write
*
* @ac: audio client pointer
- * @len: lenght in bytes
+ * @len: length in bytes
* @msw_ts: timestamp msw
* @lsw_ts: timestamp lsw
* @wflags: flags associated with write
_
Patches currently in -mm which might be from houweitaoo@xxxxxxxxx are
