From: Michael Ellerman <michael@ellerman.id.au>
To: Milton Miller <miltonm@bga.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Initialise spinlock in the DEBUG_PAGEALLOC code
Date: Wed, 18 Apr 2007 11:38:48 +1000 [thread overview]
Message-ID: <1176860328.4987.15.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <076a5a3adc4b5b29a3fd2ade48d52184@bga.com>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
On Tue, 2007-04-17 at 02:57 -0500, Milton Miller wrote:
> On Tue Apr 17 11:43:12 EST 2007, Michael Ellerman wrote:
> > -static spinlock_t linear_map_hash_lock;
> > +static spinlock_t linear_map_hash_lock = SPIN_LOCK_UNLOCKED;
>
> I think the people in this thread
>
> [KJ][PATCH]SPIN_LOCK_UNLOCKED cleanup in arch/powerpc
> http://ozlabs.org/pipermail/linuxppc-dev/2007-April/034210.html
>
> SPIN_LOCK_UNLOCKED cleanup,use DEFINE_SPINLOCK or
> __SPIN_LOCK_UNLOCKED where ever appropriate.
>
> would like you to initialize it differently. (I think it has
> to do with the lock dependancy stuff).
And it's documented where .. ?
I'll send a new patch.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-18 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 1:43 [PATCH] Initialise spinlock in the DEBUG_PAGEALLOC code Michael Ellerman
2007-04-17 7:57 ` Milton Miller
2007-04-18 1:38 ` Michael Ellerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-18 1:50 Michael Ellerman
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=1176860328.4987.15.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=paulus@samba.org \
/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;
as well as URLs for NNTP newsgroup(s).