From: Wang Hai <wanghai38@huawei.com>
To: <richard@nod.at>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH -next 1/4] ubifs: Fix 'hash' kernel-doc warning in auth.c
Date: Mon, 14 Sep 2020 21:56:51 +0800 [thread overview]
Message-ID: <20200914135654.55120-2-wanghai38@huawei.com> (raw)
In-Reply-To: <20200914135654.55120-1-wanghai38@huawei.com>
Fixes the following W=1 kernel build warning(s):
fs/ubifs/auth.c:66: warning: Excess function parameter 'hash' description in 'ubifs_prepare_auth_node'
Rename hash to inhash.
Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: Wang Hai <wanghai38@huawei.com>
---
fs/ubifs/auth.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ubifs/auth.c b/fs/ubifs/auth.c
index cc5c0abfd536..b93b3cd10bfd 100644
--- a/fs/ubifs/auth.c
+++ b/fs/ubifs/auth.c
@@ -54,7 +54,7 @@ static int ubifs_hash_calc_hmac(const struct ubifs_info *c, const u8 *hash,
* ubifs_prepare_auth_node - Prepare an authentication node
* @c: UBIFS file-system description object
* @node: the node to calculate a hash for
- * @hash: input hash of previous nodes
+ * @inhash: input hash of previous nodes
*
* This function prepares an authentication node for writing onto flash.
* It creates a HMAC from the given input hash and writes it to the node.
--
2.17.1
next prev parent reply other threads:[~2020-09-14 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 13:56 [PATCH -next 0/4] ubifs: Fix some kernel-doc warnings for ubifs Wang Hai
2020-09-14 13:56 ` Wang Hai [this message]
2020-09-14 13:56 ` [PATCH -next 2/4] ubifs: Fix some kernel-doc warnings in gc.c Wang Hai
2020-09-14 13:56 ` [PATCH -next 3/4] ubifs: Fix some kernel-doc warnings in replay.c Wang Hai
2020-09-14 13:56 ` [PATCH -next 4/4] ubifs: Fix some kernel-doc warnings in tnc.c Wang Hai
2020-09-17 21:01 ` [PATCH -next 0/4] ubifs: Fix some kernel-doc warnings for ubifs Richard Weinberger
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=20200914135654.55120-2-wanghai38@huawei.com \
--to=wanghai38@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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®