summaryrefslogtreecommitdiff
path: root/security/selinux
diff options
context:
space:
mode:
authorXiong Zhenwu <xiong.zhenwu@zte.com.cn>2021-03-08 03:03:38 -0800
committerPaul Moore <paul@paul-moore.com>2021-03-08 19:44:30 -0500
commit63ddf1baa0e34c8e2cc2dde3adb67d56984cef7a (patch)
tree010e2bd4741dce8fcabdccdc9948d53027a1bc31 /security/selinux
parent2554a48f44370a8a73e23c58c389ae9d33effb4b (diff)
selinux: fix misspellings using codespell tool
A typo is found out by codespell tool in 16th line of hashtab.c $ codespell ./security/selinux/ss/ ./hashtab.c:16: rouding ==> rounding Fix a typo found by codespell. Signed-off-by: Xiong Zhenwu <xiong.zhenwu@zte.com.cn> [PM: subject line tweak] Signed-off-by: Paul Moore <paul@paul-moore.com>
Diffstat (limited to 'security/selinux')
-rw-r--r--security/selinux/ss/hashtab.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/security/selinux/ss/hashtab.c b/security/selinux/ss/hashtab.c
index 3881787ce492..b8f6b3e0a921 100644
--- a/security/selinux/ss/hashtab.c
+++ b/security/selinux/ss/hashtab.c
@@ -13,7 +13,7 @@ static struct kmem_cache *hashtab_node_cachep __ro_after_init;
/*
* Here we simply round the number of elements up to the nearest power of two.
- * I tried also other options like rouding down or rounding to the closest
+ * I tried also other options like rounding down or rounding to the closest
* power of two (up or down based on which is closer), but I was unable to
* find any significant difference in lookup/insert performance that would
* justify switching to a different (less intuitive) formula. It could be that