From: Roland Dreier <rdreier@cisco.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Milind Arun Choudhary <milindchoudhary@GMAIL.COM>,
kernel-janitors@lists.osdl.org, kernelnewbies@nl.linux.org,
linux-kernel@vger.kernel.org
Subject: Re: [KJ] remove SPIN_LOCK_UNLOCKED
Date: Tue, 10 Apr 2007 21:13:02 +0000 [thread overview]
Message-ID: <adafy78orvl.fsf@cisco.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0704102249290.32056@yvahk01.tjqt.qr> (Jan Engelhardt's message of "Tue, 10 Apr 2007 22:50:28 +0200 (MEST)")
> Fact is, we cannot remove SPIN_LOCK_UNLOCKED. It's needed for
> variables outside functions:
>
> static spinlock_t foobar = SPIN_LOCK_UNLOCKED;
DEFINE_SPINLOCK() is provided to define variables that way.
- R.
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors
WARNING: multiple messages have this Message-ID (diff)
From: Roland Dreier <rdreier@cisco.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Milind Arun Choudhary <milindchoudhary@GMAIL.COM>,
kernel-janitors@lists.osdl.org, kernelnewbies@nl.linux.org,
linux-kernel@vger.kernel.org
Subject: Re: [KJ]remove SPIN_LOCK_UNLOCKED
Date: Tue, 10 Apr 2007 14:13:02 -0700 [thread overview]
Message-ID: <adafy78orvl.fsf@cisco.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0704102249290.32056@yvahk01.tjqt.qr> (Jan Engelhardt's message of "Tue, 10 Apr 2007 22:50:28 +0200 (MEST)")
> Fact is, we cannot remove SPIN_LOCK_UNLOCKED. It's needed for
> variables outside functions:
>
> static spinlock_t foobar = SPIN_LOCK_UNLOCKED;
DEFINE_SPINLOCK() is provided to define variables that way.
- R.
next prev parent reply other threads:[~2007-04-10 21:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 18:16 [KJ]remove SPIN_LOCK_UNLOCKED Milind Arun Choudhary
2007-04-10 18:28 ` [KJ] remove SPIN_LOCK_UNLOCKED Milind Arun Choudhary
2007-04-10 20:50 ` Jan Engelhardt
2007-04-10 20:50 ` [KJ]remove SPIN_LOCK_UNLOCKED Jan Engelhardt
2007-04-10 21:13 ` Roland Dreier [this message]
2007-04-10 21:13 ` Roland Dreier
2007-04-10 21:25 ` [KJ] remove SPIN_LOCK_UNLOCKED Robert P. J. Day
2007-04-10 21:25 ` [KJ]remove SPIN_LOCK_UNLOCKED Robert P. J. Day
2007-04-10 21:28 ` [KJ] remove SPIN_LOCK_UNLOCKED Jan Engelhardt
2007-04-10 21:28 ` [KJ]remove SPIN_LOCK_UNLOCKED Jan Engelhardt
2007-04-10 21:42 ` [KJ] remove SPIN_LOCK_UNLOCKED Roland Dreier
2007-04-10 21:42 ` [KJ]remove SPIN_LOCK_UNLOCKED Roland Dreier
2007-04-10 21:45 ` [KJ] remove SPIN_LOCK_UNLOCKED Robert P. J. Day
2007-04-10 21:45 ` [KJ]remove SPIN_LOCK_UNLOCKED Robert P. J. Day
2007-04-10 21:58 ` [KJ] remove SPIN_LOCK_UNLOCKED Roland Dreier
2007-04-10 21:58 ` [KJ]remove SPIN_LOCK_UNLOCKED Roland Dreier
2007-04-10 22:08 ` [KJ] remove SPIN_LOCK_UNLOCKED Matthew Wilcox
2007-04-10 22:08 ` Matthew Wilcox
2007-04-11 4:09 ` Milind Arun Choudhary
2007-04-11 4:21 ` Milind Arun Choudhary
2007-04-11 5:47 ` Robert P. J. Day
2007-04-11 5:47 ` Robert P. J. Day
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=adafy78orvl.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=jengelh@linux01.gwdg.de \
--cc=kernel-janitors@lists.osdl.org \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=milindchoudhary@GMAIL.COM \
/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.