On Wed, Nov 15, 2006 at 02:40:53PM -0800, Chris Wright wrote:
> * Zachary Amsden ([EMAIL PROTECTED]) wrote:
> > I'm a little worried after seeing failures to apply and missed patches 
> > that we could have other things missing from the upstream path.  Is 
> > there an easy way for us to look at diffs between the trees?  Just a 
> > diff on arch/i386 and include/asm-i386 would tell me wonders, no matter 
> > how much extra activity has gone on there.
> 
> Last night I rebased against 2.6.15-mm2.  I'm adding four patches that
> Andrew sent Andi last night.  I'll rediff and see what (if anything) is
> outstanding.

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 operatio
n
ICECREAM[14067]: Compiled on 10.23.204.76




_______________________________________________
Virtualization mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/virtualization

Reply via email to