linux-kernel - Re: sparc64 build breakage...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4977DB47.7040805@kernel.org>
Date:	Wed, 21 Jan 2009 18:34:47 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	David Miller <davem@...emloft.net>
CC:	mpm@...enic.com, mingo@...e.hu, linux-kernel@...r.kernel.org
Subject: Re: sparc64 build breakage...

David Miller wrote:
> This change:
> 
> commit d7e51e66899f95dabc89b4d4c6674a6e50fa37fc
> Author: Yinghai Lu <yinghai@...nel.org>
> Date:   Wed Jan 7 15:03:13 2009 -0800
> 
>     sparseirq: make some func to be used with genirq
> 
> breaks the sparc64 build:
> 
> arch/sparc/kernel/irq_64.c: In function ‘show_interrupts’:
> arch/sparc/kernel/irq_64.c:188: error: ‘struct kernel_stat’ has no member named ‘irqs’
> make[1]: *** [arch/sparc/kernel/irq_64.o] Error 1
> 


sorry, i missed it. we didn't touch m68k, s390, sparc...
but forget sparc64 sparc are merged already.

arch/sparc/kernel/irq_32.c:                                 kstat_cpu(j).irqs[i]);
arch/sparc/kernel/irq_32.c:     kstat_cpu(cpu).irqs[irq]++;
arch/sparc/kernel/irq_32.c:     kstat_cpu(cpu).irqs[irq]++;
arch/sparc/kernel/irq_64.c:                     seq_printf(p, "%10u ", kstat_cpu(j).irqs[i]);
arch/sparc/kernel/sun4d_irq.c:                         kstat_cpu(cpu_logical_map(x)).irqs[i]);
arch/sparc/kernel/sun4d_irq.c:  kstat_cpu(cpu).irqs[irq]++;

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/