All of lore.kernel.org
 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>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	linux-gpio@vger.kernel.org
Subject: [PATCH 7/7] gpiolib: Use spinlock_t instead of struct spinlock
Date: Thu,  4 Jul 2019 17:38:03 +0200	[thread overview]
Message-ID: <20190704153803.12739-8-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: Linus Walleij <linus.walleij@linaro.org>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: linux-gpio@vger.kernel.org
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
 drivers/gpio/gpiolib.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpio/gpiolib.h b/drivers/gpio/gpiolib.h
index 7a65dad43932c..7c52c2442173e 100644
--- a/drivers/gpio/gpiolib.h
+++ b/drivers/gpio/gpiolib.h
@@ -210,7 +210,7 @@ int gpiod_set_array_value_complex(bool raw, bool can_sleep,
 				  struct gpio_array *array_info,
 				  unsigned long *value_bitmap);
 
-extern struct spinlock gpio_lock;
+extern spinlock_t gpio_lock;
 extern struct list_head gpio_devices;
 
 struct gpio_desc {
-- 
2.20.1


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

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 15:37 [PATCH 0/7] Use spinlock_t instead of struct spinlock Sebastian Andrzej Siewior
2019-07-04 15:37 ` [PATCH 1/7] crypto: ux500: " Sebastian Andrzej Siewior
2019-07-26 12:10   ` 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 12:09     ` Thomas Gleixner
2019-07-26 22:50     ` Andrew Morton
2019-07-27  6:13       ` Thomas Gleixner
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-04 15:38   ` Sebastian Andrzej Siewior
2019-07-06 10:02   ` Greg Kroah-Hartman
2019-07-06 10:02     ` Greg Kroah-Hartman
2019-07-06 21:35     ` Sebastian Andrzej Siewior
2019-07-06 21:35       ` Sebastian Andrzej Siewior
2019-07-15 19:19   ` Greg Kroah-Hartman
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 4/7] staging: most: Use spinlock_t " Sebastian Andrzej Siewior
2019-07-04 15:38 ` [PATCH 5/7] watchdog: ie6xx_wdt: " 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 ` Sebastian Andrzej Siewior [this message]
2019-07-05  9:33   ` [PATCH 7/7] gpiolib: " 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-8-bigeasy@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=bgolaszewski@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@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 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.