Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

wireguard: global: fix spelling mistakes in comments

This fixes two spelling errors in source code comments.

Signed-off-by: Josh Soref <jsoref@gmail.com>
[Jason: rewrote commit message]
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

authored by jsoref.tngl.sh and committed by

David S. Miller a2ec8b57 d7c68a38

+5 -5
+1 -1
drivers/net/wireguard/receive.c
··· 380 380 /* We've already verified the Poly1305 auth tag, which means this packet 381 381 * was not modified in transit. We can therefore tell the networking 382 382 * stack that all checksums of every layer of encapsulation have already 383 - * been checked "by the hardware" and therefore is unneccessary to check 383 + * been checked "by the hardware" and therefore is unnecessary to check 384 384 * again in software. 385 385 */ 386 386 skb->ip_summed = CHECKSUM_UNNECESSARY;
+4 -4
include/uapi/linux/wireguard.h
··· 18 18 * one but not both of: 19 19 * 20 20 * WGDEVICE_A_IFINDEX: NLA_U32 21 - * WGDEVICE_A_IFNAME: NLA_NUL_STRING, maxlen IFNAMESIZ - 1 21 + * WGDEVICE_A_IFNAME: NLA_NUL_STRING, maxlen IFNAMSIZ - 1 22 22 * 23 23 * The kernel will then return several messages (NLM_F_MULTI) containing the 24 24 * following tree of nested items: 25 25 * 26 26 * WGDEVICE_A_IFINDEX: NLA_U32 27 - * WGDEVICE_A_IFNAME: NLA_NUL_STRING, maxlen IFNAMESIZ - 1 27 + * WGDEVICE_A_IFNAME: NLA_NUL_STRING, maxlen IFNAMSIZ - 1 28 28 * WGDEVICE_A_PRIVATE_KEY: NLA_EXACT_LEN, len WG_KEY_LEN 29 29 * WGDEVICE_A_PUBLIC_KEY: NLA_EXACT_LEN, len WG_KEY_LEN 30 30 * WGDEVICE_A_LISTEN_PORT: NLA_U16 ··· 77 77 * WGDEVICE_A_IFINDEX and WGDEVICE_A_IFNAME: 78 78 * 79 79 * WGDEVICE_A_IFINDEX: NLA_U32 80 - * WGDEVICE_A_IFNAME: NLA_NUL_STRING, maxlen IFNAMESIZ - 1 80 + * WGDEVICE_A_IFNAME: NLA_NUL_STRING, maxlen IFNAMSIZ - 1 81 81 * WGDEVICE_A_FLAGS: NLA_U32, 0 or WGDEVICE_F_REPLACE_PEERS if all current 82 82 * peers should be removed prior to adding the list below. 83 83 * WGDEVICE_A_PRIVATE_KEY: len WG_KEY_LEN, all zeros to remove ··· 121 121 * filling in information not contained in the prior. Note that if 122 122 * WGDEVICE_F_REPLACE_PEERS is specified in the first message, it probably 123 123 * should not be specified in fragments that come after, so that the list 124 - * of peers is only cleared the first time but appened after. Likewise for 124 + * of peers is only cleared the first time but appended after. Likewise for 125 125 * peers, if WGPEER_F_REPLACE_ALLOWEDIPS is specified in the first message 126 126 * of a peer, it likely should not be specified in subsequent fragments. 127 127 *