From: Roland Dreier <rolandd@cisco.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: dwalker@mvista.com, mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RT: epca_lock to DEFINE_SPINLOCK
Date: Wed, 28 Sep 2005 09:06:33 -0700 [thread overview]
Message-ID: <52irwlmb1y.fsf@cisco.com> (raw)
In-Reply-To: <1127900349.2893.19.camel@laptopd505.fenrus.org> (Arjan van de Ven's message of "Wed, 28 Sep 2005 11:39:09 +0200")
Arjan> this is really ugly though; at minimum a DEFINE_STATIC_SPINLOCK()
Arjan> would be needed to make this less ugly.
huh? This is a totally standard kernel idiom -- just do
grep -Er 'static (DECLARE|DEFINE)' .
in a kernel tree to see how prevalent it is.
- R.
next prev parent reply other threads:[~2005-09-28 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 18:32 [PATCH] RT: epca_lock to DEFINE_SPINLOCK Daniel Walker
2005-09-27 22:34 ` Thomas Gleixner
2005-09-28 9:33 ` Ingo Molnar
2005-09-28 9:39 ` Arjan van de Ven
2005-09-28 15:54 ` Daniel Walker
2005-09-28 16:06 ` Roland Dreier [this message]
2005-09-28 20:43 ` Nikita Danilov
2005-09-29 6:49 ` Steven Rostedt
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=52irwlmb1y.fsf@cisco.com \
--to=rolandd@cisco.com \
--cc=arjan@infradead.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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