[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210308110338.259868-1-xiong.zhenwu@zte.com.cn>
Date: Mon, 8 Mar 2021 03:03:38 -0800
From: menglong8.dong@...il.com
To: paul@...l-moore.com
Cc: stephen.smalley.work@...il.com, eparis@...isplace.org,
omosnace@...hat.com, xiong.zhenwu@....com.cn,
selinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH] security/selinux/ss: fix misspellings using codespell tool
From: Xiong Zhenwu <xiong.zhenwu@....com.cn>
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@....com.cn>
---
security/selinux/ss/hashtab.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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
--
2.25.1
Powered by blists - more mailing lists