From: Chris Wright <chrisw@sous-sol.org>
To: Andi Kleen <ak@suse.de>
Cc: Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@muc.de>
Subject: Re: [PATCH 1/5] Skip timer works.patch
Date: Wed, 15 Nov 2006 19:37:03 -0800 [thread overview]
Message-ID: <20061116033703.GV1397@sequoia.sous-sol.org> (raw)
In-Reply-To: <20061116032702.GH9579@bingen.suse.de>
* Andi Kleen (ak@suse.de) wrote:
> I got Andrew's patches now but the result doesn't compile as earlier
> (on SUSE 10.0, gcc 4.0)
>
> I'll adapt my old make-it-compile patch that fixed the inline assembly.
> Hopefully it'll work then.
>
> -Andi
>
> /home/lsrc/quilt/linux/kernel/spinlock.c: In function '_spin_lock_irqsave':
> include2/asm/spinlock.h:59: error: invalid 'asm': operand number missing after %
> -letter
> include2/asm/spinlock.h:59: error: invalid 'asm': operand number missing after %
> -letter
> include2/asm/spinlock.h:59: error: invalid 'asm': operand number missing after %
> -letter
> include2/asm/spinlock.h:59: error: invalid 'asm': operand number missing after %
> -letter
> include2/asm/spinlock.h:59: error: invalid 'asm': operand number missing after %
> -letter
> include2/asm/spinlock.h:59: error: invalid 'asm': operand number missing after %
> -letter
> include2/asm/spinlock.h:59: error: invalid 'asm': operand number missing after %
> -letter
> include2/asm/spinlock.h:59: error: invalid 'asm': operand number missing after %
> -letter
> {standard input}: Assembler messages:
> {standard input}:593: Error: undefined symbol `paravirt_ops' in operation
> {standard input}:593: Error: undefined symbol `PARAVIRT_irq_enable' in operation
> {standard input}:605: Error: undefined symbol `paravirt_ops' in operation
> {standard input}:605: Error: undefined symbol `PARAVIRT_irq_disable' in operation
That should be fixed (it is over here). Is ff quilt stuff uptodate?
I can sync up with it and diff to see what you might be missing.
> ICECREAM[14067]: Compiled on 10.23.204.76
mmm, ice cream ;-)
thanks,
-chris
next prev parent reply other threads:[~2006-11-16 3:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 0:09 [PATCH 1/5] Skip timer works.patch Zachary Amsden
2006-10-27 14:56 ` Andi Kleen
2006-10-27 19:09 ` Zachary Amsden
2006-10-27 21:16 ` Andi Kleen
2006-10-30 20:54 ` Zachary Amsden
2006-10-30 22:50 ` Andi Kleen
2006-10-30 23:09 ` Zachary Amsden
2006-10-30 23:12 ` Andi Kleen
2006-10-30 23:24 ` Zachary Amsden
2006-10-30 23:50 ` Andi Kleen
2006-11-15 8:03 ` Chris Wright
2006-11-15 8:21 ` Zachary Amsden
2006-11-15 22:40 ` Chris Wright
2006-11-15 22:54 ` Chris Wright
2006-11-16 3:27 ` Andi Kleen
2006-11-16 3:37 ` Chris Wright [this message]
2006-11-16 3:37 ` Andi Kleen
2006-11-16 5:06 ` Andrew Morton
2006-11-16 6:13 ` Zachary Amsden
2006-11-16 7:23 ` Andi Kleen
2006-11-16 7:02 ` Andi Kleen
2006-11-16 7:16 ` Chris Wright
2006-11-16 8:26 ` Chris Wright
2006-11-16 10:28 ` Chris Wright
2006-11-16 13:16 ` Andi Kleen
2006-11-16 19:03 ` Chris Wright
2006-11-16 19:46 ` Andi Kleen
2006-11-16 20:24 ` Chris Wright
2006-11-17 4:47 ` Andi Kleen
2006-11-17 7:33 ` Chris Wright
2006-11-17 7:38 ` Andi Kleen
2006-11-16 22:53 ` Andrew Morton
2006-11-16 23:08 ` Zachary Amsden
2006-11-16 23:10 ` Chris Wright
2006-11-17 5:05 ` Andi Kleen
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=20061116033703.GV1397@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=ak@muc.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=virtualization@lists.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;
as well as URLs for NNTP newsgroup(s).