linux-kernel - Re: [Xen-devel] Re: linux-next: Tree for July 25 (xen)

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: <20110804223259.GB4370@dumpdata.com>
Date:	Thu, 4 Aug 2011 18:32:59 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	xen-devel@...ts.xensource.com, LKML <linux-kernel@...r.kernel.org>,
	virtualization@...ts.linux-foundation.org,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-next@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [Xen-devel] Re: linux-next: Tree for July 25 (xen)

> > > These build failures are still triggering upstream:
> > > 
> > >  arch/x86/xen/trace.c:44:2: error: array index in initializer not of integer type
> > >  arch/x86/xen/trace.c:44:2: error: (near initialization for ‘xen_hypercall_names’)
> > >  arch/x86/xen/trace.c:45:1: error: ‘__HYPERVISOR_arch_4’ undeclared here (not in a function)
> > >  arch/x86/xen/trace.c:45:2: error: array index in initializer not of integer type
> > >  arch/x86/xen/trace.c:45:2: error: (near initialization for ‘xen_hypercall_names’)
> > 
> > Oh, that I haven't seen. Can you send me the .config for that please.
> 
> You can't be trying very hard then.  I see lots of these (but no,

Ah, I am getting it now. Thanks for reporting it.
--
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/