Re: linux-next: build warnings after merge of the final tree

2012-01-04 Thread hpan...@gmail.com
I thought it had been...? Need to investigate (as baby permits...) Stephen Rothwell wrote: >Hi again, > >On Thu, 22 Dec 2011 16:33:04 +1100 Stephen Rothwell > wrote: >> >> On Wed, 14 Dec 2011 08:47:01 -0800 "H. Peter Anvin" >wrote: >> > >> > On 12/14/2011 08:32 AM, Steven Rostedt wrote: >> > >

Re: linux-next: build warnings after merge of the final tree

2012-01-04 Thread Stephen Rothwell
Hi again, On Thu, 22 Dec 2011 16:33:04 +1100 Stephen Rothwell wrote: > > On Wed, 14 Dec 2011 08:47:01 -0800 "H. Peter Anvin" wrote: > > > > On 12/14/2011 08:32 AM, Steven Rostedt wrote: > > > On Wed, 2011-12-14 at 18:15 +1100, Stephen Rothwell wrote: > > > > > >> Maybe caused by commit d5e553d

Re: linux-next: build warnings after merge of the final tree

2011-12-21 Thread Stephen Rothwell
Hi Peter, On Wed, 14 Dec 2011 08:47:01 -0800 "H. Peter Anvin" wrote: > > On 12/14/2011 08:32 AM, Steven Rostedt wrote: > > On Wed, 2011-12-14 at 18:15 +1100, Stephen Rothwell wrote: > > > >> Maybe caused by commit d5e553d6e0a4 ("trace: Include > >> in trace_syscalls.c") from the tip tree. Thes

Re: linux-next: build warnings after merge of the final tree

2011-12-14 Thread H. Peter Anvin
On 12/14/2011 08:32 AM, Steven Rostedt wrote: > On Wed, 2011-12-14 at 18:15 +1100, Stephen Rothwell wrote: > >> Maybe caused by commit d5e553d6e0a4 ("trace: Include >> in trace_syscalls.c") from the tip tree. These warnings may have been >> here for a while as it is hard to catch the new ones am

Re: linux-next: build warnings after merge of the final tree

2011-12-14 Thread Steven Rostedt
On Wed, 2011-12-14 at 18:15 +1100, Stephen Rothwell wrote: > Maybe caused by commit d5e553d6e0a4 ("trace: Include > in trace_syscalls.c") from the tip tree. These warnings may have been > here for a while as it is hard to catch the new ones among the flood. > hpa, Was this change only needed

Re: linux-next: build warnings after merge of the final tree (tip treee related)

2010-09-15 Thread Ingo Molnar
* Stephen Rothwell wrote: > Hi Yinghai, > > On Tue, 14 Sep 2010 16:00:06 -0700 Yinghai Lu wrote: > > > > Also, we may need to remove all extern and __init and __initdata etc in .h > > files. > > > > please check > > > > [PATCH -v3] memblock: Fix section mismatch warning > > > > Use __init_

Re: linux-next: build warnings after merge of the final tree (tip treee related)

2010-09-14 Thread Stephen Rothwell
Hi Yinghai, On Tue, 14 Sep 2010 16:00:06 -0700 Yinghai Lu wrote: > > Also, we may need to remove all extern and __init and __initdata etc in .h > files. > > please check > > [PATCH -v3] memblock: Fix section mismatch warning > > Use __init_memblock to replace __init, and remove __init in memb

Re: linux-next: build warnings after merge of the final tree (tip treee related)

2010-09-14 Thread Stephen Rothwell
Hi Yinghai, On Tue, 14 Sep 2010 18:33:34 -0700 Yinghai Lu wrote: > > On 09/14/2010 05:29 PM, Stephen Rothwell wrote: > > > > Do not remove the "extern" key word. > > why? you got another warning? It is normal C coding practice to mark declarations in header files with extern. It probably does

Re: linux-next: build warnings after merge of the final tree (tip treee related)

2010-09-14 Thread Yinghai Lu
On 09/14/2010 05:29 PM, Stephen Rothwell wrote: > Hi Yinghai, > > On Tue, 14 Sep 2010 16:00:06 -0700 Yinghai Lu wrote: >> >> Also, we may need to remove all extern and __init and __initdata etc in .h >> files. > > Do not remove the "extern" key word. > why? you got another warning? Yinghai _

Re: linux-next: build warnings after merge of the final tree (tip treee related)

2010-09-14 Thread Stephen Rothwell
Hi Yinghai, On Tue, 14 Sep 2010 16:00:06 -0700 Yinghai Lu wrote: > > Also, we may need to remove all extern and __init and __initdata etc in .h > files. Do not remove the "extern" key word. -- Cheers, Stephen Rothwells...@canb.auug.org.au http://www.canb.auug.org.au/~sfr/

Re: linux-next: build warnings after merge of the final tree (tip treee related)

2010-09-14 Thread Yinghai Lu
On 09/13/2010 09:50 PM, Stephen Rothwell wrote: > Hi Yinghai, > > On Mon, 13 Sep 2010 01:24:20 -0700 Yinghai Lu wrote: >> >> On 09/12/2010 09:39 PM, Stephen Rothwell wrote: >>> >>> Your patch fixes some of the warnings, but still leaves these for a >>> powerpc allnoconfig build: >>> >>> WARNING:

Re: linux-next: build warnings after merge of the final tree (tip treee related)

2010-09-13 Thread Stephen Rothwell
Hi Yinghai, On Mon, 13 Sep 2010 01:24:20 -0700 Yinghai Lu wrote: > > On 09/12/2010 09:39 PM, Stephen Rothwell wrote: > > > > Your patch fixes some of the warnings, but still leaves these for a > > powerpc allnoconfig build: > > > > WARNING: mm/built-in.o(.text+0x25d80): Section mismatch in refe

Re: linux-next: build warnings after merge of the final tree (tip treee related)

2010-09-13 Thread Yinghai Lu
On 09/12/2010 09:39 PM, Stephen Rothwell wrote: > > Your patch fixes some of the warnings, but still leaves these for a > powerpc allnoconfig build: > > WARNING: mm/built-in.o(.text+0x25d80): Section mismatch in reference from the > function memblock_double_array() to the function .init.text:me

Re: linux-next: build warnings after merge of the final tree (tip treee related)

2010-09-12 Thread Yinghai Lu
On 09/12/2010 08:27 PM, Stephen Rothwell wrote: > Hi all, > > After merging the scsi-post-merge tree, today's linux-next build (powerpc > allnoconfig, i386 defconfig and others) produced these warnings (I build > with CONFIG_DEBUG_SECTION_MISMATCH=y): > > WARNING: mm/built-in.o(.text+0x25910): Se

Re: linux-next: build warnings after merge of the final tree (tip treee related)

2010-09-12 Thread Stephen Rothwell
Hi Yinghai, On Sun, 12 Sep 2010 21:14:15 -0700 Yinghai Lu wrote: > > please check it, and it should get into core/memblock branch. > > Thanks > > Yinghai > > [PATCH] memblock: Fix section mismatch warning > > for arches that use memblock other than x86 > > Reported-by: Stephen Rothwell > Si