From: Matthew Wilcox <willy@debian.org>
To: Ralf Baechle <ralf@linux-mips.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Jeff Dike <jdike@karaya.com>
Cc: linux-mips@linux-mips.org, user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] asm/smplock.h is dead
Date: Wed, 22 Oct 2003 00:09:32 +0100 [thread overview]
Message-ID: <20031021230932.GM18370@parcelfarce.linux.theplanet.co.uk> (raw)
asm/smplock.h is dead, you're the only three arches that still have it.
Can you delete next time you merge? Thanks.
$ find -type f |xargs grep smplock.h
./arch/mips/sibyte/sb1250/bcm1250_tbprof.c:#include <asm/smplock.h>
./include/asm-h8300/smplock.h: * <asm/smplock.h>
./include/asm-um/smplock.h:#include "asm/arch/smplock.h"
$ find -name smplock.h
./include/asm-h8300/smplock.h
./include/asm-mips/smplock.h
./include/asm-um/smplock.h
(the sibyte driver can just lose this line. it doesn't do any SMP locking)
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2003-10-21 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 23:09 Matthew Wilcox [this message]
2003-10-22 16:11 ` [uml-devel] Re: asm/smplock.h is dead Yoshinori Sato
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=20031021230932.GM18370@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=jdike@karaya.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=ysato@users.sourceforge.jp \
/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