Re: [PATCH] powerpc: fix function annotations to avoid section mismatch warnings with gcc-10

is wrong. > > [...] Applied to powerpc/next. [1/1] powerpc: fix function annotations to avoid section mismatch warnings with gcc-10 https://git.kernel.org/powerpc/c/aff779515a070df7e23da9e86f1096f7d10d647e cheers

Re: [PATCH] powerpc: fix function annotations to avoid section mismatch warnings with gcc-10

Hello, Michael, - Original Message - > From: "Michael Ellerman" > Subject: Re: [PATCH] powerpc: fix function annotations to avoid section > mismatch warnings with gcc-10 > ... > >> > So what changed? These functions were inlined with older

Re: [PATCH] powerpc: fix function annotations to avoid section mismatch warnings with gcc-10

it prom_init() -> setup_secure_guest() >> > > __init xive_spapr_init() -> xive_spapr_disabled() >> > >> > So what changed? These functions were inlined with older compilers, but >> > not anymore? >> >> Yes, exactly. Gcc-10 does not inline

Re: [PATCH] powerpc: fix function annotations to avoid section mismatch warnings with gcc-10

d() > > > > So what changed? These functions were inlined with older compilers, but > > not anymore? > > Yes, exactly. Gcc-10 does not inline them anymore. If this is because of my > build system, this can happen to others also. > > The same thing was fixed by

Re: [PATCH] powerpc: fix function annotations to avoid section mismatch warnings with gcc-10

20 4:49:49 PM > Subject: Re: [PATCH] powerpc: fix function annotations to avoid section > mismatch warnings with gcc-10 > > On Wed, Jul 29, 2020 at 03:37:41PM +0200, Vladis Dronov wrote: > > Certain warnings are emitted for powerpc code when building with a gcc-10 > > toolset:

Re: [PATCH] powerpc: fix function annotations to avoid section mismatch warnings with gcc-10

On Wed, Jul 29, 2020 at 03:37:41PM +0200, Vladis Dronov wrote: > Certain warnings are emitted for powerpc code when building with a gcc-10 > toolset: > > WARNING: modpost: vmlinux.o(.text.unlikely+0x377c): Section mismatch in > reference from the function remove_pmd_table() to the

[PATCH] powerpc: fix function annotations to avoid section mismatch warnings with gcc-10

Certain warnings are emitted for powerpc code when building with a gcc-10 toolset: WARNING: modpost: vmlinux.o(.text.unlikely+0x377c): Section mismatch in reference from the function remove_pmd_table() to the function .meminit.text:split_kernel_mapping() The function

[PATCH AUTOSEL 5.6 016/606] gcc-10: mark more functions __init to avoid section mismatch warnings

From: Linus Torvalds commit e99332e7b4cda6e60f5b5916cf9943a79dbef902 upstream. It seems that for whatever reason, gcc-10 ends up not inlining a couple of functions that used to be inlined before. Even if they only have one single callsite - it looks like gcc may have decided that the code was

[PATCH 5.6 132/194] gcc-10: mark more functions __init to avoid section mismatch warnings

From: Linus Torvalds commit e99332e7b4cda6e60f5b5916cf9943a79dbef902 upstream. It seems that for whatever reason, gcc-10 ends up not inlining a couple of functions that used to be inlined before. Even if they only have one single callsite - it looks like gcc may have decided that the code was

[PATCH 5.4 101/147] gcc-10: mark more functions __init to avoid section mismatch warnings

From: Linus Torvalds commit e99332e7b4cda6e60f5b5916cf9943a79dbef902 upstream. It seems that for whatever reason, gcc-10 ends up not inlining a couple of functions that used to be inlined before. Even if they only have one single callsite - it looks like gcc may have decided that the code was

[PATCH AUTOSEL 5.6 59/62] gcc-10: mark more functions __init to avoid section mismatch warnings

From: Linus Torvalds [ Upstream commit e99332e7b4cda6e60f5b5916cf9943a79dbef902 ] It seems that for whatever reason, gcc-10 ends up not inlining a couple of functions that used to be inlined before. Even if they only have one single callsite - it looks like gcc may have decided that the code

[PATCH AUTOSEL 5.4 46/49] gcc-10: mark more functions __init to avoid section mismatch warnings

From: Linus Torvalds [ Upstream commit e99332e7b4cda6e60f5b5916cf9943a79dbef902 ] It seems that for whatever reason, gcc-10 ends up not inlining a couple of functions that used to be inlined before. Even if they only have one single callsite - it looks like gcc may have decided that the code

[PATCH 4.4 035/266] powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()

From: Michael Ellerman commit 501a78cbc17c329fabf8e9750a1e9ab810c88a0e upstream. The recent LPM changes to setup_rfi_flush() are causing some section mismatch warnings because we removed the __init annotation on setup_rfi_flush(): The function setup_rfi_flush() references the function

[PATCH v2 0/2] modpost: skip section mismatch warnings on ELF local symbols by default

modpost reports section mismatch warnings on ELF local symbols. This caused false positive warnings to be reported for a local symbol name that would otherwise be elided by matching against a name pattern. This was observed using a RISC-V gcc 8.2.0 toolchain that generates section anchors

[PATCH v2 0/2] modpost: skip section mismatch warnings on ELF local symbols by default

modpost reports section mismatch warnings on ELF local symbols. This caused false positive warnings to be reported for a local symbol name that would otherwise be elided by matching against a name pattern. This was observed using a RISC-V gcc 8.2.0 toolchain that generates section anchors

Re: [PATCH 0/2] modpost: skip section mismatch warnings on ELF local symbols by default

Hi Sam, On Sat, 20 Oct 2018, Sam Ravnborg wrote: modpost is not supposed to be used outside the kernel build. And therefore if we introduce a new option then the infrastructure to enable that option should also be in place. In this particular case I cannot see why we should add the possibility

Re: [PATCH 0/2] modpost: skip section mismatch warnings on ELF local symbols by default

Hi Sam, On Sat, 20 Oct 2018, Sam Ravnborg wrote: modpost is not supposed to be used outside the kernel build. And therefore if we introduce a new option then the infrastructure to enable that option should also be in place. In this particular case I cannot see why we should add the possibility

Re: [PATCH 0/2] modpost: skip section mismatch warnings on ELF local symbols by default

Hi Paul. > modpost: skip section mismatch warnings on ELF local symbols by default > > modpost, by default, reports section mismatch warnings on ELF local > symbols. This caused false positive warnings to be reported for a > local symbol name that would otherwise be elided by m

Re: [PATCH 0/2] modpost: skip section mismatch warnings on ELF local symbols by default

Hi Paul. > modpost: skip section mismatch warnings on ELF local symbols by default > > modpost, by default, reports section mismatch warnings on ELF local > symbols. This caused false positive warnings to be reported for a > local symbol name that would otherwise be elided by m

[PATCH 0/2] modpost: skip section mismatch warnings on ELF local symbols by default

modpost: skip section mismatch warnings on ELF local symbols by default modpost, by default, reports section mismatch warnings on ELF local symbols. This caused false positive warnings to be reported for a local symbol name that would otherwise be elided by matching against a name pattern

[PATCH 0/2] modpost: skip section mismatch warnings on ELF local symbols by default

modpost: skip section mismatch warnings on ELF local symbols by default modpost, by default, reports section mismatch warnings on ELF local symbols. This caused false positive warnings to be reported for a local symbol name that would otherwise be elided by matching against a name pattern

[PATCH 4.9 45/61] powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 501a78cbc17c329fabf8e9750a1e9ab810c88a0e upstream. The recent LPM changes to setup_rfi_flush() are causing some section mismatch warnings because we removed the __init

[PATCH 4.9 45/61] powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 501a78cbc17c329fabf8e9750a1e9ab810c88a0e upstream. The recent LPM changes to setup_rfi_flush() are causing some section mismatch warnings because we removed the __init

[PATCH 4.14 055/496] powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman <m...@ellerman.id.au> commit 501a78cbc17c329fabf8e9750a1e9ab810c88a0e upstream. The recent LPM changes to setup_rfi_flush() are causing some section mismatch warnings b

[PATCH 4.14 055/496] powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 501a78cbc17c329fabf8e9750a1e9ab810c88a0e upstream. The recent LPM changes to setup_rfi_flush() are causing some section mismatch warnings because we removed the __init

Re: [PATCH] staging: bcm2835-camera: Fix module section mismatch warnings.

On Mon, May 14, 2018 at 08:44:11AM +0100, Eric Anholt wrote: > Noticed by Stephen Rothwell in -next. > > Signed-off-by: Eric Anholt > Fixes: 4bebb0312ea9 ("staging/bcm2835-camera: Set ourselves up as a platform > driver.") > Cc: Stephen Rothwell Should

Re: [PATCH] staging: bcm2835-camera: Fix module section mismatch warnings.

On Mon, May 14, 2018 at 08:44:11AM +0100, Eric Anholt wrote: > Noticed by Stephen Rothwell in -next. > > Signed-off-by: Eric Anholt > Fixes: 4bebb0312ea9 ("staging/bcm2835-camera: Set ourselves up as a platform > driver.") > Cc: Stephen Rothwell Should be: Reported-by: Stephen Rothwell I'll

[PATCH] staging: bcm2835-camera: Fix module section mismatch warnings.

Noticed by Stephen Rothwell in -next. Signed-off-by: Eric Anholt Fixes: 4bebb0312ea9 ("staging/bcm2835-camera: Set ourselves up as a platform driver.") Cc: Stephen Rothwell --- Note: only compile tested here.

[PATCH] staging: bcm2835-camera: Fix module section mismatch warnings.

Noticed by Stephen Rothwell in -next. Signed-off-by: Eric Anholt Fixes: 4bebb0312ea9 ("staging/bcm2835-camera: Set ourselves up as a platform driver.") Cc: Stephen Rothwell --- Note: only compile tested here. .../staging/vc04_services/bcm2835-camera/bcm2835-camera.c | 8 1 file

Re: [PATCH v3] powerpc/64: Fix section mismatch warnings for early boot symbols

On 04/09/2018 11:51 PM, Michael Ellerman wrote: Thanks for picking this one up. I hate to be a pain ... but before we merge this and proliferate these names, I'd like to change the names of some of these early asm functions. They're terribly named due to historical reasons. Indeed :) No

Re: [PATCH v3] powerpc/64: Fix section mismatch warnings for early boot symbols

On 04/09/2018 11:51 PM, Michael Ellerman wrote: Thanks for picking this one up. I hate to be a pain ... but before we merge this and proliferate these names, I'd like to change the names of some of these early asm functions. They're terribly named due to historical reasons. Indeed :) No

Re: [PATCH v3] powerpc/64: Fix section mismatch warnings for early boot symbols

so not to rename the powerpc code/symbol names. > > Subject: [PATCH] powerpc/64: quieten section mismatch warnings > From: Nicholas Piggin > Date: Fri Dec 23 00:14:19 AEDT 2016 > > This resolves the following section mismatch warnings: > > WARNING: vmlin

Re: [PATCH v3] powerpc/64: Fix section mismatch warnings for early boot symbols

mes. > > Subject: [PATCH] powerpc/64: quieten section mismatch warnings > From: Nicholas Piggin > Date: Fri Dec 23 00:14:19 AEDT 2016 > > This resolves the following section mismatch warnings: > > WARNING: vmlinux.o(.text+0x2fa8): Section mismatch in

[PATCH v3] powerpc/64: Fix section mismatch warnings for early boot symbols

up, we may not be able to tolerate a branch trampoline to reach the init function. Credits: code and message are based on 2016 patch by Nicholas Piggin, and slightly modified so not to rename the powerpc code/symbol names. Subject: [PATCH] powerpc/64: quieten section mismatch warnings From

[PATCH v3] powerpc/64: Fix section mismatch warnings for early boot symbols

up, we may not be able to tolerate a branch trampoline to reach the init function. Credits: code and message are based on 2016 patch by Nicholas Piggin, and slightly modified so not to rename the powerpc code/symbol names. Subject: [PATCH] powerpc/64: quieten section mismatch warnings From

[PATCH 3.2 021/104] modpost: don't emit section mismatch warnings for compiler optimizations

3.2.101-rc1 review patch. If anyone has any objections, please let me know. -- From: Paul Gortmaker commit 4a3893d069b788f3570c19c12d9e986e8e15870f upstream. Currently an allyesconfig build [gcc-4.9.1] can generate the following: WARNING:

[PATCH 3.2 021/104] modpost: don't emit section mismatch warnings for compiler optimizations

3.2.101-rc1 review patch. If anyone has any objections, please let me know. -- From: Paul Gortmaker commit 4a3893d069b788f3570c19c12d9e986e8e15870f upstream. Currently an allyesconfig build [gcc-4.9.1] can generate the following: WARNING: vmlinux.o(.text.unlikely+0x3864):

[PATCH v2] powerpc/64: Fix section mismatch warnings for early boot symbols

up, we may not be able to tolerate a branch trampoline to reach the init function. Credits: code and message are based on 2016 patch by Nicholas Piggin, and slightly modified so not to rename the powerpc code/symbol names. Subject: [PATCH] powerpc/64: quieten section mismatch warnings From

[PATCH v2] powerpc/64: Fix section mismatch warnings for early boot symbols

up, we may not be able to tolerate a branch trampoline to reach the init function. Credits: code and message are based on 2016 patch by Nicholas Piggin, and slightly modified so not to rename the powerpc code/symbol names. Subject: [PATCH] powerpc/64: quieten section mismatch warnings From

[PATCH] powerpc/64: Fix section mismatch warnings for early boot symbols

up, we may not be able to tolerate a branch trampoline to reach the init function. Credits: code and message are based on 2016 patch by Nicholas Piggin, and slightly modified so not to rename the powerpc code/symbol names. Subject: [PATCH] powerpc/64: quieten section mismatch warnings From

[PATCH] powerpc/64: Fix section mismatch warnings for early boot symbols

up, we may not be able to tolerate a branch trampoline to reach the init function. Credits: code and message are based on 2016 patch by Nicholas Piggin, and slightly modified so not to rename the powerpc code/symbol names. Subject: [PATCH] powerpc/64: quieten section mismatch warnings From

[PATCH 3.16 205/294] modpost: don't emit section mismatch warnings for compiler optimizations

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Paul Gortmaker commit 4a3893d069b788f3570c19c12d9e986e8e15870f upstream. Currently an allyesconfig build [gcc-4.9.1] can generate the following: WARNING:

[PATCH 3.16 205/294] modpost: don't emit section mismatch warnings for compiler optimizations

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Paul Gortmaker commit 4a3893d069b788f3570c19c12d9e986e8e15870f upstream. Currently an allyesconfig build [gcc-4.9.1] can generate the following: WARNING: vmlinux.o(.text.unlikely+0x3864):

Re: [PATCH] omap: hwmod: fix section mismatch warnings

* Arnd Bergmann [170915 12:46]: > Older compilers choose not to inline _setup_clkctrl_provider(), > leading to a harmless warning: > > WARNING: vmlinux.o(.text+0x27b34): Section mismatch in reference from the > function _setup_clkctrl_provider() to the function >

Re: [PATCH] omap: hwmod: fix section mismatch warnings

* Arnd Bergmann [170915 12:46]: > Older compilers choose not to inline _setup_clkctrl_provider(), > leading to a harmless warning: > > WARNING: vmlinux.o(.text+0x27b34): Section mismatch in reference from the > function _setup_clkctrl_provider() to the function >

[PATCH] omap: hwmod: fix section mismatch warnings

Older compilers choose not to inline _setup_clkctrl_provider(), leading to a harmless warning: WARNING: vmlinux.o(.text+0x27b34): Section mismatch in reference from the function _setup_clkctrl_provider() to the function .init.text:memblock_virt_alloc_try_nid() The function

[PATCH] omap: hwmod: fix section mismatch warnings

Older compilers choose not to inline _setup_clkctrl_provider(), leading to a harmless warning: WARNING: vmlinux.o(.text+0x27b34): Section mismatch in reference from the function _setup_clkctrl_provider() to the function .init.text:memblock_virt_alloc_try_nid() The function

[PATCH 3.18 64/68] modpost: dont emit section mismatch warnings for compiler optimizations

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Gortmaker commit 4a3893d069b788f3570c19c12d9e986e8e15870f upstream. Currently an allyesconfig build [gcc-4.9.1] can generate the following: WARNING:

[PATCH 3.18 64/68] modpost: dont emit section mismatch warnings for compiler optimizations

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Gortmaker commit 4a3893d069b788f3570c19c12d9e986e8e15870f upstream. Currently an allyesconfig build [gcc-4.9.1] can generate the following: WARNING: vmlinux.o(.text.unlikely+0x3864):

arch/x86: sfi: intel_scu_devices_create() section mismatch warnings

I noticed the following in my build logs: WARNING: vmlinux.o(.text+0xa90d8): Section mismatch in reference from the function intel_scu_devices_create() to the function .init.text:i2c_register_board_info() The function intel_scu_devices_create() references the function __init

arch/x86: sfi: intel_scu_devices_create() section mismatch warnings

I noticed the following in my build logs: WARNING: vmlinux.o(.text+0xa90d8): Section mismatch in reference from the function intel_scu_devices_create() to the function .init.text:i2c_register_board_info() The function intel_scu_devices_create() references the function __init

Re: [PATCH 2/2] modpost: don't emit section mismatch warnings for compiler optimizations

Paul Gortmaker writes: > Currently an allyesconfig build [gcc-4.9.1] can generate the following: > >WARNING: vmlinux.o(.text.unlikely+0x3864): Section mismatch in >reference from the function cpumask_empty.constprop.3() to the >variable .init.data:nmi_ipi_mask > > which comes from the

[PATCH 2/2] modpost: don't emit section mismatch warnings for compiler optimizations

Currently an allyesconfig build [gcc-4.9.1] can generate the following: WARNING: vmlinux.o(.text.unlikely+0x3864): Section mismatch in reference from the function cpumask_empty.constprop.3() to the variable .init.data:nmi_ipi_mask which comes from the cpumask_empty usage in

[PATCH 2/2] modpost: don't emit section mismatch warnings for compiler optimizations

Currently an allyesconfig build [gcc-4.9.1] can generate the following: WARNING: vmlinux.o(.text.unlikely+0x3864): Section mismatch in reference from the function cpumask_empty.constprop.3() to the variable .init.data:nmi_ipi_mask which comes from the cpumask_empty usage in

Re: [PATCH 2/2] modpost: don't emit section mismatch warnings for compiler optimizations

Paul Gortmaker paul.gortma...@windriver.com writes: Currently an allyesconfig build [gcc-4.9.1] can generate the following: WARNING: vmlinux.o(.text.unlikely+0x3864): Section mismatch in reference from the function cpumask_empty.constprop.3() to the variable .init.data:nmi_ipi_mask

Re: [PATCH] gianfar: Fix the section mismatch warnings.

From: Xiubo Li Date: Wed, 4 Jun 2014 16:49:16 +0800 > Building with CONFIG_DEBUG_SECTION_MISMATCH enabled, the following > WARNING is occured: > > LD drivers/net/built-in.o > WARNING: drivers/net/built-in.o(.text+0xcd4c): Section mismatch in > reference from the function gfar_probe() to

[PATCH] gianfar: Fix the section mismatch warnings.

Building with CONFIG_DEBUG_SECTION_MISMATCH enabled, the following WARNING is occured: LD drivers/net/built-in.o WARNING: drivers/net/built-in.o(.text+0xcd4c): Section mismatch in reference from the function gfar_probe() to the function .init.text:gfar_init_addr_hash_table() The function

[PATCH] gianfar: Fix the section mismatch warnings.

Building with CONFIG_DEBUG_SECTION_MISMATCH enabled, the following WARNING is occured: LD drivers/net/built-in.o WARNING: drivers/net/built-in.o(.text+0xcd4c): Section mismatch in reference from the function gfar_probe() to the function .init.text:gfar_init_addr_hash_table() The function

Re: [PATCH] gianfar: Fix the section mismatch warnings.

From: Xiubo Li li.xi...@freescale.com Date: Wed, 4 Jun 2014 16:49:16 +0800 Building with CONFIG_DEBUG_SECTION_MISMATCH enabled, the following WARNING is occured: LD drivers/net/built-in.o WARNING: drivers/net/built-in.o(.text+0xcd4c): Section mismatch in reference from the function

[PATCH] xen: resolve section mismatch warnings in xen-acpi-processor

The following resolves a section mismatch warning below in xen-acpi-processor introduced by 3fac10145b766a2244422788f62dc35978613fd8 [13/13] xen: Re-upload processor PM data to hypervisor after S3 resume (v2) Warning: WARNING: drivers/xen/built-in.o(.text+0x2056a): Section mismatch in reference

[PATCH] xen: resolve section mismatch warnings

--- drivers/xen/xen-acpi-processor.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/xen/xen-acpi-processor.c b/drivers/xen/xen-acpi-processor.c index 86b6f69..285e3d5 100644 --- a/drivers/xen/xen-acpi-processor.c +++ b/drivers/xen/xen-acpi-processor.c @@ -470,7

[PATCH] xen: resolve section mismatch warnings

--- drivers/xen/xen-acpi-processor.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/xen/xen-acpi-processor.c b/drivers/xen/xen-acpi-processor.c index 86b6f69..285e3d5 100644 --- a/drivers/xen/xen-acpi-processor.c +++ b/drivers/xen/xen-acpi-processor.c @@ -470,7

[PATCH] xen: resolve section mismatch warnings in xen-acpi-processor

The following resolves a section mismatch warning below in xen-acpi-processor introduced by 3fac10145b766a2244422788f62dc35978613fd8 [13/13] xen: Re-upload processor PM data to hypervisor after S3 resume (v2) Warning: WARNING: drivers/xen/built-in.o(.text+0x2056a): Section mismatch in reference

[for-next][PATCH 6/6] tracing: Fix some section mismatch warnings

From: Li Zefan As we've added __init annotation to field-defining functions, we should add __refdata annotation to event_call variables, which reference those functions. Link: http://lkml.kernel.org/r/51343c1f.2050...@huawei.com Reported-by: Fengguang Wu Signed-off-by: Li Zefan

[for-next][PATCH 6/6] tracing: Fix some section mismatch warnings

From: Li Zefan lize...@huawei.com As we've added __init annotation to field-defining functions, we should add __refdata annotation to event_call variables, which reference those functions. Link: http://lkml.kernel.org/r/51343c1f.2050...@huawei.com Reported-by: Fengguang Wu

[PATCH 10/17] ARM: s3c24xx: fix multiple section mismatch warnings

The *_irq_add function should not be marked __init because the driver subsystem thinks they might be called at a later stage. The usb_simtec_init function accesses initdata and should be marked init. This is safe because the only caller is also an init function. Without this patch, building

[PATCH 10/17] ARM: s3c24xx: fix multiple section mismatch warnings

The *_irq_add function should not be marked __init because the driver subsystem thinks they might be called at a later stage. The usb_simtec_init function accesses initdata and should be marked init. This is safe because the only caller is also an init function. Without this patch, building

Re: [PATCH v2] media: davinci: fix section mismatch warnings

Hi Prabhakar, Thanks for the patch. On Tuesday 14 August 2012 10:53:09 Prabhakar Lad wrote: > From: Lad, Prabhakar > > This patch fixes section mismatch warnings for > davinci video drivers. > > Signed-off-by: Lad, Prabhakar > Signed-off-by: Manjunath Hadli Acked

Re: [PATCH v2] media: davinci: fix section mismatch warnings

Hi Prabhakar, Thanks for the patch. On Tuesday 14 August 2012 10:53:09 Prabhakar Lad wrote: From: Lad, Prabhakar prabhakar@ti.com This patch fixes section mismatch warnings for davinci video drivers. Signed-off-by: Lad, Prabhakar prabhakar@ti.com Signed-off-by: Manjunath Hadli

[PATCH v2] media: davinci: fix section mismatch warnings

From: Lad, Prabhakar This patch fixes section mismatch warnings for davinci video drivers. Signed-off-by: Lad, Prabhakar Signed-off-by: Manjunath Hadli --- Changes for v2: 1: Annotate probe with __devinit. 2: Fixed the commit message. drivers/media/video/davinci/dm355_ccdc.c |2

[PATCH v2] media: davinci: fix section mismatch warnings

From: Lad, Prabhakar prabhakar@ti.com This patch fixes section mismatch warnings for davinci video drivers. Signed-off-by: Lad, Prabhakar prabhakar@ti.com Signed-off-by: Manjunath Hadli manjunath.ha...@ti.com --- Changes for v2: 1: Annotate probe with __devinit. 2: Fixed the commit

Re: [Fixed PATCH] hpt366: fix section mismatch warnings

On Sun, Feb 24, 2008 at 03:33:51PM +0100, Bartlomiej Zolnierkiewicz wrote: > On Saturday 23 February 2008, Sam Ravnborg wrote: > > hpt366: fix section mismatch warnings > > > > Fix following warnings: > > WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mism

Re: [Fixed PATCH] hpt366: fix section mismatch warnings

On Saturday 23 February 2008, Sam Ravnborg wrote: > hpt366: fix section mismatch warnings > > Fix following warnings: > WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mismatch in reference > from the variable hpt37x_info.0 to the variable .devinit.data:hpt370 >

Re: [Fixed PATCH] hpt366: fix section mismatch warnings

On Saturday 23 February 2008, Sam Ravnborg wrote: hpt366: fix section mismatch warnings Fix following warnings: WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mismatch in reference from the variable hpt37x_info.0 to the variable .devinit.data:hpt370 WARNING: o-sparc64/vmlinux.o

Re: [Fixed PATCH] hpt366: fix section mismatch warnings

On Sun, Feb 24, 2008 at 03:33:51PM +0100, Bartlomiej Zolnierkiewicz wrote: On Saturday 23 February 2008, Sam Ravnborg wrote: hpt366: fix section mismatch warnings Fix following warnings: WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mismatch in reference from the variable

[Fixed PATCH] hpt366: fix section mismatch warnings

hpt366: fix section mismatch warnings Fix following warnings: WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mismatch in reference from the variable hpt37x_info.0 to the variable .devinit.data:hpt370 WARNING: o-sparc64/vmlinux.o(.data+0x195a40): Section mismatch in reference from

[Fixed PATCH] hpt366: fix section mismatch warnings

hpt366: fix section mismatch warnings Fix following warnings: WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mismatch in reference from the variable hpt37x_info.0 to the variable .devinit.data:hpt370 WARNING: o-sparc64/vmlinux.o(.data+0x195a40): Section mismatch in reference from

Re: [PATCH] hpt366: fix section mismatch warnings

On Friday 22 February 2008, Sergei Shtylyov wrote: > Sam Ravnborg wrote: > > > hpt366: fix section mismatch warnings > > > Fix following warnings: > > WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mismatch in reference > > from the varia

Re: [PATCH] hpt366: fix section mismatch warnings

> @@ -1570,11 +1570,13 @@ static int __devinit hpt366_init_one(struct pci_dev > *dev, const struct pci_devic > if (rev < 3) > info = > else { > - static const struct hpt_info *hpt37x_info[] = > - {

Re: [PATCH] hpt366: fix section mismatch warnings

Sam Ravnborg wrote: hpt366: fix section mismatch warnings Fix following warnings: WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mismatch in reference from the variable hpt37x_info.0 to the variable .devinit.data:hpt370 WARNING: o-sparc64/vmlinux.o(.data+0x195a40): Section mismatch

[PATCH] hpt366: fix section mismatch warnings

hpt366: fix section mismatch warnings Fix following warnings: WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mismatch in reference from the variable hpt37x_info.0 to the variable .devinit.data:hpt370 WARNING: o-sparc64/vmlinux.o(.data+0x195a40): Section mismatch in reference from

[PATCH] hpt366: fix section mismatch warnings

hpt366: fix section mismatch warnings Fix following warnings: WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mismatch in reference from the variable hpt37x_info.0 to the variable .devinit.data:hpt370 WARNING: o-sparc64/vmlinux.o(.data+0x195a40): Section mismatch in reference from

Re: [PATCH] hpt366: fix section mismatch warnings

Sam Ravnborg wrote: hpt366: fix section mismatch warnings Fix following warnings: WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mismatch in reference from the variable hpt37x_info.0 to the variable .devinit.data:hpt370 WARNING: o-sparc64/vmlinux.o(.data+0x195a40): Section mismatch

Re: [PATCH] hpt366: fix section mismatch warnings

@@ -1570,11 +1570,13 @@ static int __devinit hpt366_init_one(struct pci_dev *dev, const struct pci_devic if (rev 3) info = hpt36x; else { - static const struct hpt_info *hpt37x_info[] = - {

Re: [PATCH] hpt366: fix section mismatch warnings

On Friday 22 February 2008, Sergei Shtylyov wrote: Sam Ravnborg wrote: hpt366: fix section mismatch warnings Fix following warnings: WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mismatch in reference from the variable hpt37x_info.0 to the variable .devinit.data:hpt370

mm section mismatch warnings for ps3

When building current mainline for ps3_defconfig, I get the following mm-related section mismatches: | WARNING: mm/built-in.o(.text+0x25094): Section mismatch in reference from the function .sparse_add_one_section() to the function .meminit.text:.sparse_index_init() | The function

Re: [PATCH 27/27] [ALSA] hdsp - fix section mismatch warnings

At Mon, 18 Feb 2008 08:45:08 +0100, Sam Ravnborg wrote: > > On Mon, Feb 18, 2008 at 07:43:32AM +0100, Takashi Iwai wrote: > > At Sun, 17 Feb 2008 13:23:04 +0100, > > Sam Ravnborg wrote: > > > > > > Fix following warnings: > > > WARNING: sound/pci/rme9652/snd-hdsp.o(.text+0x34bc): Section

Re: [PATCH 27/27] [ALSA] hdsp - fix section mismatch warnings

At Mon, 18 Feb 2008 08:45:08 +0100, Sam Ravnborg wrote: On Mon, Feb 18, 2008 at 07:43:32AM +0100, Takashi Iwai wrote: At Sun, 17 Feb 2008 13:23:04 +0100, Sam Ravnborg wrote: Fix following warnings: WARNING: sound/pci/rme9652/snd-hdsp.o(.text+0x34bc): Section mismatch in

mm section mismatch warnings for ps3

When building current mainline for ps3_defconfig, I get the following mm-related section mismatches: | WARNING: mm/built-in.o(.text+0x25094): Section mismatch in reference from the function .sparse_add_one_section() to the function .meminit.text:.sparse_index_init() | The function

Re: [PATCH 27/27] [ALSA] hdsp - fix section mismatch warnings

On Mon, Feb 18, 2008 at 07:43:32AM +0100, Takashi Iwai wrote: > At Sun, 17 Feb 2008 13:23:04 +0100, > Sam Ravnborg wrote: > > > > Fix following warnings: > > WARNING: sound/pci/rme9652/snd-hdsp.o(.text+0x34bc): Section mismatch in > > reference from the function hdsp_check_for_firmware() to the

Re: [PATCH 27/27] [ALSA] hdsp - fix section mismatch warnings

At Sun, 17 Feb 2008 13:23:04 +0100, Sam Ravnborg wrote: > > Fix following warnings: > WARNING: sound/pci/rme9652/snd-hdsp.o(.text+0x34bc): Section mismatch in > reference from the function hdsp_check_for_firmware() to the function > .devinit.text:hdsp_request_fw_loader() > WARNING:

Re: [PATCH 17/27] acer-wmi: fix section mismatch warnings

On Sun, Feb 17, 2008 at 01:03:55PM +, Carlos Corbacho wrote: > On Sunday 17 February 2008 12:22:54 Sam Ravnborg wrote: > > Fix following warnings: > > WARNING: vmlinux.o(.text+0x672615): Section mismatch in reference from the > > function acer_platform_remove() to the function > >

Re: [PATCH 17/27] acer-wmi: fix section mismatch warnings

On Sunday 17 February 2008 12:22:54 Sam Ravnborg wrote: > Fix following warnings: > WARNING: vmlinux.o(.text+0x672615): Section mismatch in reference from the > function acer_platform_remove() to the function > .exit.text:acer_backlight_exit() WARNING: vmlinux.o(.devinit.text+0x1e859): > Section

[PATCH 05/27] cpu: fix section mismatch warnings in hotcpu_register

Fix following warnings: WARNING: vmlinux.o(.data+0x5020): Section mismatch in reference from the variable cpu_vsyscall_notifier_nb.12876 to the function .cpuinit.text:cpu_vsyscall_notifier() WARNING: vmlinux.o(.data+0x9ce0): Section mismatch in reference from the variable

[PATCH 17/27] acer-wmi: fix section mismatch warnings

Fix following warnings: WARNING: vmlinux.o(.text+0x672615): Section mismatch in reference from the function acer_platform_remove() to the function .exit.text:acer_backlight_exit() WARNING: vmlinux.o(.devinit.text+0x1e859): Section mismatch in reference from the function acer_platform_probe() to

[PATCH 01/27] serial: silence section mismatch warnings in 8250_pci

Fix following warnings: WARNING: drivers/serial/built-in.o(.data+0x5b8): Section mismatch in reference from the variable pci_serial_quirks to the function .devexit.text:pci_ite887x_exit() WARNING: drivers/serial/built-in.o(.data+0x5e0): Section mismatch in reference from the variable

[PATCH 27/27] [ALSA] hdsp - fix section mismatch warnings

Fix following warnings: WARNING: sound/pci/rme9652/snd-hdsp.o(.text+0x34bc): Section mismatch in reference from the function hdsp_check_for_firmware() to the function .devinit.text:hdsp_request_fw_loader() WARNING: sound/pci/rme9652/snd-hdsp.o(.text+0x4ac6): Section mismatch in reference from

[PATCH 15/27] cpufreq: fix section mismatch warnings

Fix the following warnings: WARNING: vmlinux.o(.text+0xfe6711): Section mismatch in reference from the function cpufreq_unregister_driver() to the variable .cpuinit.data:cpufreq_cpu_notifier WARNING: vmlinux.o(.text+0xfe68af): Section mismatch in reference from the function

[PATCH 18/27] video: fix section mismatch warnings in uvesafb

Fix following warnings: WARNING: vmlinux.o(.text+0x51961b): Section mismatch in reference from the function param_set_scroll() to the variable .devinit.data:mtrr WARNING: vmlinux.o(.text+0x519641): Section mismatch in reference from the function param_set_scroll() to the variable

[PATCH 07/27] cpu: fix section mismatch warnings in *cpu_down

Fix following warnings: WARNING: vmlinux.o(.text+0x75c8d): Section mismatch in reference from the function take_cpu_down() to the variable .cpuinit.data:cpu_chain WARNING: vmlinux.o(.text+0x75d2a): Section mismatch in reference from the function _cpu_down() to the variable

  1   2   3   4   5   >