From: Andrew Morton <akpm@osdl.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: blaisorblade@yahoo.it, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net, domen@coderock.org,
amitg@calsoftinc.com, gud@eth.net
Subject: [uml-devel] Re: [patch 1/1] unified spinlock initialization arch/um/drivers/port_kern.c
Date: Wed, 9 Mar 2005 14:50:44 -0800 [thread overview]
Message-ID: <20050309145044.764bc056.akpm@osdl.org> (raw)
In-Reply-To: <20050309224259.J25398@flint.arm.linux.org.uk>
Russell King <rmk+lkml@arm.linux.org.uk> wrote:
>
> I'm not convinced about the practicality of converting all static
> initialisations to code-based initialisations though
This is the first one I recall seeing. All the other conversions were replacing
static spinlock_t lock = SPIN_LOCK_UNLOCKED;
with
static DEFINE_SPINLOCK(lock);
and replacing
{
lock = SPIN_LOCK_UNLOCKED;
}
with
{
spin_lock_init(lock);
}
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-03-09 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 9:42 [uml-devel] [patch 1/1] unified spinlock initialization arch/um/drivers/port_kern.c blaisorblade
2005-03-09 17:12 ` [uml-devel] " Russell King
2005-03-09 19:52 ` Blaisorblade
2005-03-09 22:42 ` Russell King
2005-03-09 22:50 ` Andrew Morton [this message]
[not found] ` <Pine.LNX.4.61.0503091840210.22633@chaos.analogic.com>
2005-03-10 2:09 ` Zwane Mwaikambo
2005-03-10 8:12 ` Thomas Gleixner
2005-03-11 19:18 ` Blaisorblade
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=20050309145044.764bc056.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=amitg@calsoftinc.com \
--cc=blaisorblade@yahoo.it \
--cc=domen@coderock.org \
--cc=gud@eth.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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