mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, Peter Zijlstra <peterz@infradead.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org
Subject: [PATCH 1/7] crypto: ux500: Use spinlock_t instead of struct spinlock
Date: Thu,  4 Jul 2019 17:37:57 +0200	[thread overview]
Message-ID: <20190704153803.12739-2-bigeasy@linutronix.de> (raw)
In-Reply-To: <20190704153803.12739-1-bigeasy@linutronix.de>

For spinlocks the type spinlock_t should be used instead of "struct
spinlock".

Use spinlock_t for spinlock's definition.

Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: linux-crypto@vger.kernel.org
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
 drivers/crypto/ux500/cryp/cryp.h     | 4 ++--
 drivers/crypto/ux500/hash/hash_alg.h | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/crypto/ux500/cryp/cryp.h b/drivers/crypto/ux500/cryp/cryp.h
index bd89504e81678..8da7f87b339b4 100644
--- a/drivers/crypto/ux500/cryp/cryp.h
+++ b/drivers/crypto/ux500/cryp/cryp.h
@@ -241,12 +241,12 @@ struct cryp_device_data {
 	struct clk *clk;
 	struct regulator *pwr_regulator;
 	int power_status;
-	struct spinlock ctx_lock;
+	spinlock_t ctx_lock;
 	struct cryp_ctx *current_ctx;
 	struct klist_node list_node;
 	struct cryp_dma dma;
 	bool power_state;
-	struct spinlock power_state_spinlock;
+	spinlock_t power_state_spinlock;
 	bool restore_dev_ctx;
 };
 
diff --git a/drivers/crypto/ux500/hash/hash_alg.h b/drivers/crypto/ux500/hash/hash_alg.h
index ab2bd00c1c365..7c9bcc15125ff 100644
--- a/drivers/crypto/ux500/hash/hash_alg.h
+++ b/drivers/crypto/ux500/hash/hash_alg.h
@@ -366,10 +366,10 @@ struct hash_device_data {
 	phys_addr_t             phybase;
 	struct klist_node	list_node;
 	struct device		*dev;
-	struct spinlock		ctx_lock;
+	spinlock_t		ctx_lock;
 	struct hash_ctx		*current_ctx;
 	bool			power_state;
-	struct spinlock		power_state_lock;
+	spinlock_t		power_state_lock;
 	struct regulator	*regulator;
 	struct clk		*clk;
 	bool			restore_dev_state;
-- 
2.20.1


  reply	other threads:[~2019-07-04 15:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 15:37 [PATCH 0/7] " Sebastian Andrzej Siewior
2019-07-04 15:37 ` Sebastian Andrzej Siewior [this message]
2019-07-26 12:10   ` [PATCH 1/7] crypto: ux500: " Thomas Gleixner
2019-07-26 12:32   ` Herbert Xu
2019-07-04 15:37 ` [PATCH 2/7] vmpressure: " Sebastian Andrzej Siewior
2019-07-26 12:09   ` Thomas Gleixner
2019-07-26 22:50     ` Andrew Morton
2019-07-27  6:13       ` Thomas Gleixner
2019-07-04 15:37 ` [PATCH 3/7] drm/vgem: " Sebastian Andrzej Siewior
2019-07-04 15:38 ` [PATCH 4/7] staging: most: " Sebastian Andrzej Siewior
2019-07-06 10:02   ` Greg Kroah-Hartman
2019-07-06 21:35     ` Sebastian Andrzej Siewior
2019-07-15 19:19   ` Greg Kroah-Hartman
2019-07-26 11:22     ` [PATCH v2] staging: most: Use DEFINE_SPINLOCK() " Thomas Gleixner
2019-07-04 15:38 ` [PATCH 5/7] watchdog: ie6xx_wdt: Use spinlock_t " Sebastian Andrzej Siewior
2019-07-08 17:55   ` Guenter Roeck
2019-07-04 15:38 ` [PATCH 6/7] nfp: " Sebastian Andrzej Siewior
2019-07-04 20:42   ` Jakub Kicinski
2019-07-05 23:18   ` David Miller
2019-07-04 15:38 ` [PATCH 7/7] gpiolib: " Sebastian Andrzej Siewior
2019-07-05  9:33   ` Bartosz Golaszewski
2019-07-06 18:15   ` Linus Walleij
2019-07-04 15:39 ` [PATCH 0/7] " David Laight
2019-07-04 15:45   ` 'Sebastian Andrzej Siewior'

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=20190704153803.12739-2-bigeasy@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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 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®