diff options
author | Petr Vaněk <arkamar@atlas.cz> | 2022-06-30 16:27:20 +0200 |
---|---|---|
committer | Steffen Klassert <steffen.klassert@secunet.com> | 2022-07-04 10:20:11 +0200 |
commit | 5e25c25aa2c08fb9a79476e029c0b1e3dcd70566 (patch) | |
tree | ac9203a272b51285a1e74127c0c7373b694e86b6 | |
parent | esp6: Fix spelling mistake (diff) | |
download | linux-5e25c25aa2c08fb9a79476e029c0b1e3dcd70566.tar.xz linux-5e25c25aa2c08fb9a79476e029c0b1e3dcd70566.zip |
xfrm: improve wording of comment above XFRM_OFFLOAD flags
I have noticed a few minor wording issues in a comment recently added
above XFRM_OFFLOAD flags in 7c76ecd9c99b ("xfrm: enforce validity of
offload input flags").
Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
-rw-r--r-- | include/uapi/linux/xfrm.h | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/include/uapi/linux/xfrm.h b/include/uapi/linux/xfrm.h index 3ed61df9cc91..7929bf9cbee4 100644 --- a/include/uapi/linux/xfrm.h +++ b/include/uapi/linux/xfrm.h @@ -511,9 +511,9 @@ struct xfrm_user_offload { int ifindex; __u8 flags; }; -/* This flag was exposed without any kernel code that supporting it. - * Unfortunately, strongswan has the code that uses sets this flag, - * which makes impossible to reuse this bit. +/* This flag was exposed without any kernel code that supports it. + * Unfortunately, strongswan has the code that sets this flag, + * which makes it impossible to reuse this bit. * * So leave it here to make sure that it won't be reused by mistake. */ |