From: Martin Kepplinger <martink@posteo.de>
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Martin Kepplinger <martink@posteo.de>
Subject: [PATCH] fs: namei: use __pure modifier as declared in headers
Date: Wed, 3 May 2017 11:00:41 +0200 [thread overview]
Message-ID: <1493802041-30353-1-git-send-email-martink@posteo.de> (raw)
sparse complains about different modifiers here. The function definitions
should simply use their declarations' modifiers.
We also shrink the text width to our 80 characters maximum while we are
at it. This makes it sparse- and checkpatch-clean.
Signed-off-by: Martin Kepplinger <martink@posteo.de>
---
fs/namei.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index d7b88c7..3d18a8c 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -1925,7 +1925,8 @@ static inline unsigned int fold_hash(unsigned long x, unsigned long y)
* payload bytes, to match the way that hash_name() iterates until it
* finds the delimiter after the name.
*/
-unsigned int full_name_hash(const void *salt, const char *name, unsigned int len)
+unsigned int __pure full_name_hash(const void *salt, const char *name,
+ unsigned int len)
{
unsigned long a, x = 0, y = (unsigned long)salt;
@@ -1946,7 +1947,7 @@ unsigned int full_name_hash(const void *salt, const char *name, unsigned int len
EXPORT_SYMBOL(full_name_hash);
/* Return the "hash_len" (hash and length) of a null-terminated string */
-u64 hashlen_string(const void *salt, const char *name)
+u64 __pure hashlen_string(const void *salt, const char *name)
{
unsigned long a = 0, x = 0, y = (unsigned long)salt;
unsigned long adata, mask, len;
--
2.1.4
reply other threads:[~2017-05-03 9:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1493802041-30353-1-git-send-email-martink@posteo.de \
--to=martink@posteo.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®