From: Roman Zippel <zippel@linux-m68k.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-arch@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: spinlock-consolidation.patch
Date: Sat, 10 Sep 2005 01:52:24 +0200 [thread overview]
Message-ID: <43222038.5010302@linux-m68k.org> (raw)
In-Reply-To: <20050909121521.12942a8d.akpm@osdl.org>
Hi,
Andrew Morton wrote:
> include/linux/spinlock_api_smp.h | 57 ++
> include/linux/spinlock_api_up.h | 80 +++
> include/linux/spinlock_types_up.h | 51 ++
> include/linux/spinlock_up.h | 74 +++
These are rather small files and not useful outside of
<linux/spinlock.h>/<linux/spinlock_types.h>. Is it really needed to keep
these separate?
bye, Roman
next prev parent reply other threads:[~2005-09-09 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 19:15 spinlock-consolidation.patch Andrew Morton
2005-09-09 19:50 ` spinlock-consolidation.patch David S. Miller
2005-09-09 23:52 ` Roman Zippel [this message]
2005-09-12 9:27 ` spinlock-consolidation.patch Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2005-09-09 21:04 spinlock-consolidation.patch Luck, Tony
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=43222038.5010302@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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