From: Mukesh Ojha <mojha@codeaurora.org>
To: Yue Haibing <yuehaibing@huawei.com>,
richard@nod.at, dedekind1@gmail.com, adrian.hunter@intel.com
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH -next] ubifs: remove unused function __ubifs_shash_final
Date: Thu, 21 Mar 2019 01:35:37 +0530 [thread overview]
Message-ID: <97289b81-ed73-002a-504d-2e82fad153e7@codeaurora.org> (raw)
In-Reply-To: <20190320140955.11576-1-yuehaibing@huawei.com>
On 3/20/2019 7:39 PM, Yue Haibing wrote:
> From: YueHaibing <yuehaibing@huawei.com>
>
> There is no callers in tree, and can be removed.
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> fs/ubifs/auth.c | 18 ------------------
> 1 file changed, 18 deletions(-)
>
> diff --git a/fs/ubifs/auth.c b/fs/ubifs/auth.c
> index 5bf5fd0..2a40ccce 100644
> --- a/fs/ubifs/auth.c
> +++ b/fs/ubifs/auth.c
> @@ -147,24 +147,6 @@ struct shash_desc *__ubifs_hash_get_desc(const struct ubifs_info *c)
> }
>
> /**
> - * __ubifs_shash_final - finalize shash
> - * @c: UBIFS file-system description object
> - * @desc: the descriptor
> - * @out: the output hash
> - *
> - * Simple wrapper around crypto_shash_final(), safe to be called with
> - * disabled authentication.
> - */
> -int __ubifs_shash_final(const struct ubifs_info *c, struct shash_desc *desc,
> - u8 *out)
> -{
> - if (ubifs_authenticated(c))
> - return crypto_shash_final(desc, out);
> -
> - return 0;
> -}
> -
> -/**
> * ubifs_bad_hash - Report hash mismatches
> * @c: UBIFS file-system description object
> * @node: the node
Looks fine to be removed.
Acked-by: Mukesh Ojha <mojha@codeaurora.org>
-Mukesh
next prev parent reply other threads:[~2019-03-20 20:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 14:09 [PATCH -next] ubifs: remove unused function __ubifs_shash_final Yue Haibing
2019-03-20 20:05 ` Mukesh Ojha [this message]
2019-03-20 20:18 ` Richard Weinberger
2019-03-21 7:54 ` Mukesh Ojha
2019-03-21 8:09 ` Richard Weinberger
2019-03-22 6:59 ` Mukesh Ojha
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=97289b81-ed73-002a-504d-2e82fad153e7@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=adrian.hunter@intel.com \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=yuehaibing@huawei.com \
/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