From: Andy Whitcroft <apw@shadowen.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
stern@rowland.harvard.edu, lenb@kernel.org, greg@kroah.com,
akpm@linux-foundation.org, rjw@sisk.pl
Subject: Re: [Build Failure] linux-next: Tree for March 18
Date: Tue, 18 Mar 2008 13:31:10 +0000 [thread overview]
Message-ID: <20080318132550.GB30500@shadowen.org> (raw)
In-Reply-To: <47DFA49D.4000007@linux.vnet.ibm.com>
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
next prev parent reply other threads:[~2008-03-18 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 9:52 linux-next: Tree for March 18 Stephen Rothwell
2008-03-18 11:16 ` [Build Failure] " Kamalesh Babulal
2008-03-18 13:31 ` Andy Whitcroft [this message]
2008-03-19 23:20 ` Stephen Rothwell
2008-03-19 23:13 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080318132550.GB30500@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.