| b.liu | e958203 | 2025-04-17 19:18:16 +0800 | [diff] [blame] | 1 | From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001 |
| 2 | From: Josh Soref <jsoref@gmail.com> |
| 3 | Date: Sun, 15 Dec 2019 22:08:02 +0100 |
| 4 | Subject: [PATCH] wireguard: global: fix spelling mistakes in comments |
| 5 | |
| 6 | commit a2ec8b5706944d228181c8b91d815f41d6dd8e7b upstream. |
| 7 | |
| 8 | This fixes two spelling errors in source code comments. |
| 9 | |
| 10 | Signed-off-by: Josh Soref <jsoref@gmail.com> |
| 11 | [Jason: rewrote commit message] |
| 12 | Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> |
| 13 | Signed-off-by: David S. Miller <davem@davemloft.net> |
| 14 | Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> |
| 15 | --- |
| 16 | drivers/net/wireguard/receive.c | 2 +- |
| 17 | include/uapi/linux/wireguard.h | 8 ++++---- |
| 18 | 2 files changed, 5 insertions(+), 5 deletions(-) |
| 19 | |
| 20 | --- a/drivers/net/wireguard/receive.c |
| 21 | +++ b/drivers/net/wireguard/receive.c |
| 22 | @@ -380,7 +380,7 @@ static void wg_packet_consume_data_done( |
| 23 | /* We've already verified the Poly1305 auth tag, which means this packet |
| 24 | * was not modified in transit. We can therefore tell the networking |
| 25 | * stack that all checksums of every layer of encapsulation have already |
| 26 | - * been checked "by the hardware" and therefore is unneccessary to check |
| 27 | + * been checked "by the hardware" and therefore is unnecessary to check |
| 28 | * again in software. |
| 29 | */ |
| 30 | skb->ip_summed = CHECKSUM_UNNECESSARY; |
| 31 | --- a/include/uapi/linux/wireguard.h |
| 32 | +++ b/include/uapi/linux/wireguard.h |
| 33 | @@ -18,13 +18,13 @@ |
| 34 | * one but not both of: |
| 35 | * |
| 36 | * WGDEVICE_A_IFINDEX: NLA_U32 |
| 37 | - * WGDEVICE_A_IFNAME: NLA_NUL_STRING, maxlen IFNAMESIZ - 1 |
| 38 | + * WGDEVICE_A_IFNAME: NLA_NUL_STRING, maxlen IFNAMSIZ - 1 |
| 39 | * |
| 40 | * The kernel will then return several messages (NLM_F_MULTI) containing the |
| 41 | * following tree of nested items: |
| 42 | * |
| 43 | * WGDEVICE_A_IFINDEX: NLA_U32 |
| 44 | - * WGDEVICE_A_IFNAME: NLA_NUL_STRING, maxlen IFNAMESIZ - 1 |
| 45 | + * WGDEVICE_A_IFNAME: NLA_NUL_STRING, maxlen IFNAMSIZ - 1 |
| 46 | * WGDEVICE_A_PRIVATE_KEY: NLA_EXACT_LEN, len WG_KEY_LEN |
| 47 | * WGDEVICE_A_PUBLIC_KEY: NLA_EXACT_LEN, len WG_KEY_LEN |
| 48 | * WGDEVICE_A_LISTEN_PORT: NLA_U16 |
| 49 | @@ -77,7 +77,7 @@ |
| 50 | * WGDEVICE_A_IFINDEX and WGDEVICE_A_IFNAME: |
| 51 | * |
| 52 | * WGDEVICE_A_IFINDEX: NLA_U32 |
| 53 | - * WGDEVICE_A_IFNAME: NLA_NUL_STRING, maxlen IFNAMESIZ - 1 |
| 54 | + * WGDEVICE_A_IFNAME: NLA_NUL_STRING, maxlen IFNAMSIZ - 1 |
| 55 | * WGDEVICE_A_FLAGS: NLA_U32, 0 or WGDEVICE_F_REPLACE_PEERS if all current |
| 56 | * peers should be removed prior to adding the list below. |
| 57 | * WGDEVICE_A_PRIVATE_KEY: len WG_KEY_LEN, all zeros to remove |
| 58 | @@ -121,7 +121,7 @@ |
| 59 | * filling in information not contained in the prior. Note that if |
| 60 | * WGDEVICE_F_REPLACE_PEERS is specified in the first message, it probably |
| 61 | * should not be specified in fragments that come after, so that the list |
| 62 | - * of peers is only cleared the first time but appened after. Likewise for |
| 63 | + * of peers is only cleared the first time but appended after. Likewise for |
| 64 | * peers, if WGPEER_F_REPLACE_ALLOWEDIPS is specified in the first message |
| 65 | * of a peer, it likely should not be specified in subsequent fragments. |
| 66 | * |