From: Eric Biggers <ebiggers@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
tglx@linutronix.de, Corentin Labbe <clabbe@baylibre.com>
Subject: Re: [PATCH 2/2] crypto: user: remove crypto_cfg_mutex
Date: Mon, 11 Feb 2019 13:22:38 -0800 [thread overview]
Message-ID: <20190211212237.GA226227@gmail.com> (raw)
In-Reply-To: <20190211110251.17377-2-bigeasy@linutronix.de>
On Mon, Feb 11, 2019 at 12:02:51PM +0100, Sebastian Andrzej Siewior wrote:
> crypto_cfg_mutex was never used since it got introduced in commit
>
> cac5818c25d04 ("crypto: user - Implement a generic crypto statistics")
>
> Cc: Corentin Labbe <clabbe@baylibre.com>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> crypto/crypto_user_stat.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/crypto/crypto_user_stat.c b/crypto/crypto_user_stat.c
> index 3e9a53233d804..028be6a1ea781 100644
> --- a/crypto/crypto_user_stat.c
> +++ b/crypto/crypto_user_stat.c
> @@ -20,8 +20,6 @@
>
> #define null_terminated(x) (strnlen(x, sizeof(x)) < sizeof(x))
>
> -static DEFINE_MUTEX(crypto_cfg_mutex);
> -
> extern struct sock *crypto_nlsk;
>
> struct crypto_dump_info {
> --
> 2.20.1
>
Hi Sebastian, this is already removed by a patch queued in cryptodev:
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git/commit/?id=554557ce0001fc0371fb88db53d7dfe2a398c6de
- Eric
next prev parent reply other threads:[~2019-02-11 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 11:02 [PATCH 1/2] crypto: chtls: remove cdev_list_lock Sebastian Andrzej Siewior
2019-02-11 11:02 ` [PATCH 2/2] crypto: user: remove crypto_cfg_mutex Sebastian Andrzej Siewior
2019-02-11 21:22 ` Eric Biggers [this message]
2019-02-22 11:56 ` [PATCH 1/2] crypto: chtls: remove cdev_list_lock Herbert Xu
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=20190211212237.GA226227@gmail.com \
--to=ebiggers@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.