From: Andrew Morton <akpm@osdl.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, kiran@scalex86.org, ak@suse.de,
md@google.com, mingo@elte.hu, pravin.shelar@calsoftinc.com,
shai@scalex86.org
Subject: Re: + spin_lock_irq-enable-interrupts-while-spinning-i386-implementation.patch added to -mm tree
Date: Sun, 7 Jan 2007 12:05:03 -0800 [thread overview]
Message-ID: <20070107120503.ceadb6ed.akpm@osdl.org> (raw)
In-Reply-To: <1168176285.26086.241.camel@imap.mvista.com>
On Sun, 07 Jan 2007 05:24:45 -0800
Daniel Walker <dwalker@mvista.com> wrote:
> Now it fails with CONFIG_PARAVIRT off .
>
> scripts/kconfig/conf -s arch/i386/Kconfig
> CHK include/linux/version.h
> CHK include/linux/compile.h
> CHK include/linux/utsrelease.h
> UPD include/linux/compile.h
> CC arch/i386/kernel/asm-offsets.s
> In file included from include/linux/spinlock.h:88,
> from include/linux/module.h:10,
> from include/linux/crypto.h:22,
> from arch/i386/kernel/asm-offsets.c:8:
> include/asm/spinlock.h: In function '__raw_spin_lock_irq':
> include/asm/spinlock.h:100: error: expected string literal before '__CLI_STI_INPUT_ARGS'
bah.
--- a/include/asm-i386/spinlock.h~spin_lock_irq-enable-interrupts-while-spinning-i386-implementation-fix-fix
+++ a/include/asm-i386/spinlock.h
@@ -14,6 +14,7 @@
#define STI_STRING "sti"
#define CLI_STI_CLOBBERS
#define CLI_STI_INPUT_ARGS
+#define __CLI_STI_INPUT_ARGS
#endif /* CONFIG_PARAVIRT */
/*
_
next prev parent reply other threads:[~2007-01-07 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200701032112.l03LCnVb031386@shell0.pdx.osdl.net>
2007-01-06 22:35 ` + spin_lock_irq-enable-interrupts-while-spinning-i386-implementation.patch added to -mm tree Daniel Walker
2007-01-07 7:26 ` Andrew Morton
2007-01-07 13:24 ` Daniel Walker
2007-01-07 14:39 ` Zachary Amsden
2007-01-07 15:17 ` Zachary Amsden
2007-01-07 20:05 ` Andrew Morton [this message]
2007-01-07 21:06 ` Ravikiran G Thirumalai
2007-01-07 21:27 ` Ravikiran G Thirumalai
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=20070107120503.ceadb6ed.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=dwalker@mvista.com \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=md@google.com \
--cc=mingo@elte.hu \
--cc=pravin.shelar@calsoftinc.com \
--cc=shai@scalex86.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).