linux-next: Tree for March 18

linux-next: Tree for March 18

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]

Hi all,

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(tar balls at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/).

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log files
in the Next directory.  Between each merge, the tree was built with
allmodconfig for both powerpc and x86_64.

There were a couple of merge conflicts (fairly trivial). (And the
expected build failure in st.c fixed by reverting the removal of struct
class_device.) Notification has been sent.

We are up to 48 trees, more are welcome (even if they are currently
empty).  The influx of new trees has been underwhelming.  Thanks to those
who have contributed, and to those who haven't, please do.

In particular, I have very few of the architecture trees ....

Status of my local build tests is at
http://kisskb.ellerman.id.au/linux-next.  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

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

[Kamalesh Babulal]

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

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.

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

[Andy Whitcroft]

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

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

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

Hi Kamalesh,

On Tue, 18 Mar 2008 16:46:45 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
>
> 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

Thanks for the report. I have reverted the patch in Greg's series that
causes the breakage until it is fixed.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

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

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 872 bytes --]

Hi Andy,

On Tue, 18 Mar 2008 13:31:10 +0000 Andy Whitcroft <apw@shadowen.org> wrote:
>
> 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.

I have today changed from using powerpc allmodconfig to ppc64_defconfig
which is faster (it was taking over 7-8 hours to create the linux-tree)
and has CONFIG_PM disabled.  I am still also doing the x86_64
allmodconfig build.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]