linux-kernel - Re: [BUILD_FAILURE] linux-next: Tree for March 31 build fails with CONFIG

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: <20080331155554.GE3696@kroah.com>
Date:	Mon, 31 Mar 2008 08:55:54 -0700
From:	Greg KH <greg@...ah.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	netdev@...r.kernel.org, Andy Whitcroft <apw@...dowen.org>,
	Christopher Harrer <charrer@...critech.com>,
	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
Subject: Re: [BUILD_FAILURE] linux-next: Tree for March 31 build fails with
	CONFIG_SLICOSS=y

On Tue, Apr 01, 2008 at 12:31:10AM +1100, Stephen Rothwell wrote:
> Hi Greg,
> 
> Strike two!  Again, these drivers need to build (or not try to build) for
> all architectures ... Its out until you tell me the above is true.
> 
> #if defined(CONFIG_X86_64)
>         hcmd->cmdsize = (ulong32) ((((ulong64) & ihcmd->u.slic_buffers.bufs[1] -
>                                      (ulong64) hcmd) + 31) >> 5);
> #elif defined(CONFIG_X86)
>         hcmd->cmdsize = ((((ulong32) & ihcmd->u.slic_buffers.bufs[1] -
>                            (ulong32) hcmd) + 31) >> 5);
> #else
>         Stop Compilation;

Ah, missed that one, that's why it built on my machines (x86-64 and
i386), but would die on anything else.  That test is just wrong, I'll
fix it up to get it to build on all arches (doesn't mean it will run
though, it assumes that port io is memory mapped flat on all machines
and still needs a lot of work to be fixed.

thanks,

greg k-h
--
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/