From: David Laight <David.Laight@ACULAB.COM>
To: 'Sebastian Andrzej Siewior' <bigeasy@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>
Subject: RE: [PATCH 0/7] Use spinlock_t instead of struct spinlock
Date: Thu, 4 Jul 2019 15:39:41 +0000 [thread overview]
Message-ID: <4456003dfa654444b8af7b7be9a9c30e@AcuMS.aculab.com> (raw)
In-Reply-To: <20190704153803.12739-1-bigeasy@linutronix.de>
From: Sebastian Andrzej Siewior
> Sent: 04 July 2019 16:38
>
> Just a small series to clean up various "struct spinlock" user and make
> them use "spinlock_t" instead.
I thought it was policy to avoid typedefs?
Probably because you can only define them once.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2019-07-04 15:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 15:37 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 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 ` David Laight [this message]
2019-07-04 15:45 ` [PATCH 0/7] " '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=4456003dfa654444b8af7b7be9a9c30e@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=bigeasy@linutronix.de \
--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
Powered by JetHome