linux-kernel - Re: [Build Failure] linux-next: Tree for March 18

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]

Date:	Tue, 18 Mar 2008 13:31:10 +0000
From:	Andy Whitcroft <apw@...dowen.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	stern@...land.harvard.edu, lenb@...nel.org, greg@...ah.com,
	akpm@...ux-foundation.org, rjw@...k.pl
Subject: Re: [Build Failure] linux-next: Tree for March 18

On Tue, Mar 18, 2008 at 04:46:45PM +0530, Kamalesh Babulal wrote:
> Hi Stephen,
> 
> The kernel build of linux-next tree(s) have been failing from 20080314 with
> the build failure
> 
> drivers/serial/serial_core.c: In function `uart_add_one_port':
> drivers/serial/serial_core.c:2359: error: invalid lvalue in assignment
> make[2]: *** [drivers/serial/serial_core.o] Error 1
> 
> And the patch was submitted for the same http://marc.info/?l=linux-next&m=120561799422065&w=2

This breakage is shown up when compiled with a config which doesn't have
CONFIG_PM set.  It is a common error to only test with that turned on
and I am sure that this is just one of a number of bugs that have been
picked up by real machine configs.

Perhaps it would be worth having one of your integration test runs be
with a configuration with CONFIG_PM disabled so that they get detected
earlier in the process.

-apw
--
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/