linux-next: build failure after merge of the powerpc tree

Hi all,

After merging the powerpc tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

arch/powerpc/include/asm/setup.h: Assembler messages:
arch/powerpc/include/asm/setup.h:6: Error: Unrecognized opcode: `extern'
make[2]: *** [arch/powerpc/kernel/head_64.o] Error 1

Caused by commit a9c0f41b3a64 ("powerpc: Add printk companion for
ppc_md.progress").  Clearly not build tested for 64 but powerpc 

I have used the version of the powerpc tree from next-20110630 for today.

--

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

Re: linux-next: build failure after merge of the powerpc tree

On Fri, 2011-07-01 at 11:39 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the powerpc tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> arch/powerpc/include/asm/setup.h: Assembler messages:
> arch/powerpc/include/asm/setup.h:6: Error: Unrecognized opcode: `extern'
> make[2]: *** [arch/powerpc/kernel/head_64.o] Error 1
> 
> Caused by commit a9c0f41b3a64 ("powerpc: Add printk companion for
> ppc_md.progress").  Clearly not build tested for 64 but powerpc 
> 
> I have used the version of the powerpc tree from next-20110630 for today.

Crap !

I had fixed that locally, and ... forgot to commit --amend before
pushing it.

I'll stick a fixup patch right next to it.

Cheers,
Ben.

where to find Linux-next-tree

Dear sir,

                     I am Ravishankar, where i can find the
linux-next-tree? to send patches.

With regards,
Ravishankar.

RE: where to find Linux-next-tree

Thanks,
Tanya Brokhman
---
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

> -----Original Message-----
> From: linux-next-owner <at> vger.kernel.org [mailto:linux-next-
> owner <at> vger.kernel.org] On Behalf Of ravi shankar
> Sent: Friday, July 01, 2011 7:02 AM
> To: linux-next <at> vger.kernel.org
> Subject: where to find Linux-next-tree
> 
> Dear sir,
> 
>                      I am Ravishankar, where i can find the
> linux-next-tree? to send patches.
> 
> With regards,
> Ravishankar.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-next"
> in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: where to find Linux-next-tree

Hi Ravishankar,

Please look at http://linux.f-seidel.de/linux-next/.
The git tree URL is at the top of the page

Thanks,
Tanya Brokhman
---
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

linux-next: build failure after merge of the akpm tree

Hi Andrew,

After merging the akpm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

arch/powerpc/kernel/rtas.c: In function 'rtas_restart':
arch/powerpc/kernel/rtas.c:655:24: error: 'SYS_RESTART' undeclared (first use in this function)
arch/powerpc/kernel/rtas.c: In function 'rtas_power_off':
arch/powerpc/kernel/rtas.c:664:24: error: 'SYS_POWER_OFF' undeclared (first use in this function)
arch/powerpc/kernel/rtas.c: In function 'rtas_halt':
arch/powerpc/kernel/rtas.c:674:24: error: 'SYS_HALT' undeclared (first use in this function)

Caused by commit ac050ff2a176 ("It is not necessary to share the same
notifier.h").

I have reverted that commit for today.

--

-- 
Cheers,
Stephen Rothwell                    sfr <at> canb.auug.org.au

Re: linux-next: build failure after merge of the akpm tree

于 2011年07月01日 13:19, Stephen Rothwell 写道:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> arch/powerpc/kernel/rtas.c: In function 'rtas_restart':
> arch/powerpc/kernel/rtas.c:655:24: error: 'SYS_RESTART' undeclared (first use in this function)
> arch/powerpc/kernel/rtas.c: In function 'rtas_power_off':
> arch/powerpc/kernel/rtas.c:664:24: error: 'SYS_POWER_OFF' undeclared (first use in this function)
> arch/powerpc/kernel/rtas.c: In function 'rtas_halt':
> arch/powerpc/kernel/rtas.c:674:24: error: 'SYS_HALT' undeclared (first use in this function)
>
> Caused by commit ac050ff2a176 ("It is not necessary to share the same
> notifier.h").

I think the following patch will fix this.

Thanks.

---

Signed-off-by: WANG Cong <amwang <at> redhat.com>

diff --git a/arch/powerpc/kernel/rtas.c b/arch/powerpc/kernel/rtas.c
index 271ff63..0e0ea94 100644
--- a/arch/powerpc/kernel/rtas.c
+++ b/arch/powerpc/kernel/rtas.c
 <at>  <at>  -24,6 +24,7  <at>  <at> 

linux-next: build failure after merge of the final tree (akpm tree related)

Hi all,

After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:

drivers/video/backlight/ams369fg06.o:(.bss+0x510): multiple definition of `before_power'
drivers/video/backlight/s6e63m0.o:(.bss+0x5e0): first defined here

Caused by commit 45193c8486ef ("Add the ams369fg06 amoled panel driver.
The ams369fg06 amoled panel (480").  The variable should probably be
static in both files.

I have applied the following patch for today:

From: Stephen Rothwell <sfr <at> canb.auug.org.au>
Date: Fri, 1 Jul 2011 15:34:22 +1000
Subject: [PATCH] backlight: make some varibales static

fixes this build error:

drivers/video/backlight/ams369fg06.o:(.bss+0x510): multiple definition of `before_power'
drivers/video/backlight/s6e63m0.o:(.bss+0x5e0): first defined here

Signed-off-by: Stephen Rothwell <sfr <at> canb.auug.org.au>
---
 drivers/video/backlight/ams369fg06.c |    2 +-
 drivers/video/backlight/s6e63m0.c    |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/video/backlight/ams369fg06.c b/drivers/video/backlight/ams369fg06.c

linux-next: Tree for July 1

Hi all,

Changes since 20110630:

New tree: akpm (a subset of mmotm - Andrew can now start eating again )

The powerpc tree gained another build failure so I used the version from
next-20110630.

The security-testing tree lost its bad merge.

The kvm tree lost its conflict.

The akpm tree gained two build failures for which I revertd a commit and
applied a patch.

----------------------------------------------------------------------------

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/v2.6/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).

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
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the

Re: linux-next: build failure after merge of the akpm tree

Hi,

On Fri, 01 Jul 2011 13:32:04 +0800 Cong Wang <amwang <at> redhat.com> wrote:
>
> 于 2011年07月01日 13:19, Stephen Rothwell 写道:
> >
> > After merging the akpm tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > arch/powerpc/kernel/rtas.c: In function 'rtas_restart':
> > arch/powerpc/kernel/rtas.c:655:24: error: 'SYS_RESTART' undeclared (first use in this function)
> > arch/powerpc/kernel/rtas.c: In function 'rtas_power_off':
> > arch/powerpc/kernel/rtas.c:664:24: error: 'SYS_POWER_OFF' undeclared (first use in this function)
> > arch/powerpc/kernel/rtas.c: In function 'rtas_halt':
> > arch/powerpc/kernel/rtas.c:674:24: error: 'SYS_HALT' undeclared (first use in this function)
> >
> > Caused by commit ac050ff2a176 ("It is not necessary to share the same
> > notifier.h").
> 
> I think the following patch will fix this.

Please find all the other files that need that include as well (there is
at least one more).

--

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