From: "Luca Falavigna" <dktrkranz@gmail.com>
To: mingo@elte.hu
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: SPIN_LOCK_UNLOCKED
Date: Fri, 24 Mar 2006 22:56:58 +0100 [thread overview]
Message-ID: <ff1cadb20603241356j7257f826n@mail.gmail.com> (raw)
Hi,
I noticed you recently changed the way you handle SPIN_LOCK_UNLOCKED macro.
Former version was something like that:
#define SPIN_LOCK_UNLOCKED(lockname) \
(spinlock_t) { { __SPIN_LOCK_UNLOCKED(lockname) } }
while current version is:
# define SPIN_LOCK_UNLOCKED \
(spinlock_t) { { __SPIN_LOCK_UNLOCKED } }
I noticed your 2.6.16-rt6 patch includes two calls to
SPIN_LOCK_UNLOCKED(lockname) macro, the first one in
arch/powerpc/kernel/rtas.c and the last one in
include/asm-powerpc/rwsem.h.
Is this the right behaviour?
Regards,
--
Luca
next reply other threads:[~2006-03-24 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 21:56 Luca Falavigna [this message]
2006-03-26 16:44 ` SPIN_LOCK_UNLOCKED Ingo Molnar
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=ff1cadb20603241356j7257f826n@mail.gmail.com \
--to=dktrkranz@gmail.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
all inboxes | Powered by JetHome®