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
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
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 the
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
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:
&g
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 function
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 remove_pmd_tab
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
u
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
u
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
u
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 wa
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 wa
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
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.
To
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
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 mat
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. This
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
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
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
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 chan
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 worrie
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
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
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):
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
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
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):
* 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
> .init.text:memblock_virt_alloc_
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 _setup_clkctrl_provide
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):
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 i2c_register_board_inf
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
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 arch/x86/kern
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 t
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 gf
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
---
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
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
Signed-off-by:
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 s3c24
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
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
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
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
>
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 the
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
> @@ -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[] =
> -
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
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 the
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 .sparse_add_on
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
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 f
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: sound/pci/rme
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
> > .exit.text:ac
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 mi
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 profile_cpu_callback_nb
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 t
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 pci_serial_
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 th
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 cpufreq_register_driv
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 .devinit.data:mt
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 .cpuinit.data:cpu_chain
Silence the following warnings:
WARNING: drivers/pcmcia/built-in.o(.data+0x348): Section mismatch in reference
from the variable pccard_sysfs_interface to the function
.devinit.text:pccard_sysfs_add_socket()
WARNING: drivers/pcmcia/built-in.o(.data+0x350): Section mismatch in reference
from the
Silence following warnings:
WARNING: drivers/pcmcia/built-in.o(.data+0x14e0): Section mismatch in reference
from the variable pd6729_pci_drv to the function
.devinit.text:pd6729_pci_probe()
WARNING: drivers/pcmcia/built-in.o(.data+0x14e8): Section mismatch in reference
from the variable pd6729_p
On Sat, Feb 02, 2008 at 10:55:10AM +0800, Denis Cheng wrote:
> the struct pci_driver refered ath5k_pci_id_table which in __devinit section,
> the sparse tool suggest this renamed to "*driver", kills mismatch warnings.
>
> Signed-off-by: Denis Cheng <[EMAIL PROTECTED]>
Sorry, I beat you to it on F
On Fri, Feb 01, 2008 at 02:38:38PM +0100, Sam Ravnborg wrote:
> drivers/isdn resulted in 34 section mismatch warnings - so
> I decided to give them a try.
> This resulted in 5 simple patches.
>
> I know Jeff Garzik has some ISDN clean-up patches pending
> but rather than waiti
2008/2/2, Denis Cheng <[EMAIL PROTECTED]>:
> the struct pci_driver refered ath5k_pci_id_table which in __devinit section,
> the sparse tool suggest this renamed to "*driver", kills mismatch warnings.
>
> Signed-off-by: Denis Cheng <[EMAIL PROTECTED]>
> ---
> drivers/net/wireless/ath5k/base.c |
On Thu, Jan 31, 2008 at 11:10:30PM +0100, Sam Ravnborg wrote:
> Fix following warnings:
> WARNING: o-x86_64/drivers/pci/built-in.o(.text+0xb054): Section mismatch in
> reference from the function cpci_configure_slot() to the function
> .devinit.text:pci_do_scan_bus()
> WARNING: o-x86_64/drivers/p
the struct pci_driver refered ath5k_pci_id_table which in __devinit section,
the sparse tool suggest this renamed to "*driver", kills mismatch warnings.
Signed-off-by: Denis Cheng <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath5k/base.c |6 +++---
1 files changed, 3 insertions(+), 3 deletion
Hi Andrew.
Again I rely on you to pick up the patches.
But let me know if you prefer another route toward mainline.
And I obviously expect the Cc: people to review the changes
albeit this serie is trivial.
This is on top of my local tree and not -mm - so yell at me
and drop anything that does no
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 pci_serial_
Silence the following warnings:
WARNING: drivers/pcmcia/built-in.o(.data+0x348): Section mismatch in reference
from the variable pccard_sysfs_interface to the function
.devinit.text:pccard_sysfs_add_socket()
WARNING: drivers/pcmcia/built-in.o(.data+0x350): Section mismatch in reference
from the
Silence following warnings:
WARNING: drivers/pcmcia/built-in.o(.data+0x14e0): Section mismatch in reference
from the variable pd6729_pci_drv to the function
.devinit.text:pd6729_pci_probe()
WARNING: drivers/pcmcia/built-in.o(.data+0x14e8): Section mismatch in reference
from the variable pd6729_p
Sam Ravnborg wrote:
I know Jeff Garzik has some ISDN clean-up patches pending
but rather than waiting forever to have them acked I deciced
to fix the warnings in the current kernel.
Please do...
Those patches are not going to be submitted for the current merge
window, as I had higher priorit
If anyone like to test it here is a cumulative patch.
Sam
diff --git a/drivers/isdn/hisax/amd7930_fn.c b/drivers/isdn/hisax/amd7930_fn.c
index c0d7036..341faf5 100644
--- a/drivers/isdn/hisax/amd7930_fn.c
+++ b/drivers/isdn/hisax/amd7930_fn.c
@@ -744,8 +744,7 @@ dbusy_timer_handler(struct
Fix the following warnings:
WARNING: drivers/isdn/hisax/built-in.o(.text+0x722): Section mismatch in
reference from the function hisax_cs_setup_card() to the function
.devinit.text:setup_teles3()
WARNING: drivers/isdn/hisax/built-in.o(.text+0x72c): Section mismatch in
reference from the function
Fix the following warnings:
WARNING: drivers/isdn/hisax/built-in.o(.text+0x1b276): Section mismatch in
reference from the function inithscxisac() to the function
.devinit.text:clear_pending_isac_ints()
WARNING: drivers/isdn/hisax/built-in.o(.text+0x1b286): Section mismatch in
reference from the
drivers/isdn resulted in 34 section mismatch warnings - so
I decided to give them a try.
This resulted in 5 simple patches.
I know Jeff Garzik has some ISDN clean-up patches pending
but rather than waiting forever to have them acked I deciced
to fix the warnings in the current kernel.
This for
* Sam Ravnborg <[EMAIL PROTECTED]> wrote:
> x86: fix section mismatch warning in acpi/boot.c
> x86: silence section mismatch warning in smpboot_64.c
> x86: fix section mismatch warning in kernel/pci-calgary
> x86: fix section mismatch warnings when ref
Fix the following warnings:
WARNING: arch/x86/kernel/built-in.o(.exit.text+0xf8): Section mismatch in
reference from the function msr_exit() to the variable
.cpuinit.data:msr_class_cpu_notifier
WARNING: arch/x86/kernel/built-in.o(.exit.text+0x158): Section mismatch in
reference from the function
Fix following warning:
WARNING: o-x86_64/kernel/built-in.o(.text+0x36d8b): Section mismatch in
reference from the function enable_nonboot_cpus() to the function
.cpuinit.text:_cpu_up()
enable_nonboot_cpus() are used solely from CONFIG_CONFIG_PM_SLEEP_SMP=y
and PM_SLEEP_SMP imply HOTPLUG_CPU ther
The hotcpu_notifier is used to create notifiers to be called later.
It really looks like the functions that are registered are only
relevant in a HOTPLUG_CPU configuration and the correct fix was
to wrap them in an #ifdef / #endif or similar.
But for now just tell modpost to silence the warning by
The following warnings were issued during build of
drivers/pci with an allyesconfig build:
WARNING: o-x86_64/drivers/pci/built-in.o(.text+0xdaf): Section mismatch in
reference from the function pci_add_new_bus() to the function
.devinit.text:pci_alloc_child_bus()
WARNING: o-x86_64/drivers/pci/bui
Fix following warnings:
WARNING: o-x86_64/drivers/pci/built-in.o(.text+0xb054): Section mismatch in
reference from the function cpci_configure_slot() to the function
.devinit.text:pci_do_scan_bus()
WARNING: o-x86_64/drivers/pci/built-in.o(.text+0x153ab): Section mismatch in
reference from the fu
The following set of patches fixes 25 Section mismatch warnings
in following directories:
kernel/
mm/
drivers/pci
arch/x86/
When build individually they are now clean.
The shortlog:
Sam Ravnborg (11):
pci: fix section mismatch warnings referring to pci_do_scan_bus
pci: fix 4x
* Sam Ravnborg <[EMAIL PROTECTED]> wrote:
> The following serie of 8 patches contains:
>
> x86: fix Section mismatch warning in srat_64.c
> => straightforward - please apply
>
> x86: fix Section mismatch warning in mcheck/mce_64.c
> => I took some assumptions on use of notifier.
>See commen
The following serie of 8 patches contains:
x86: fix Section mismatch warning in srat_64.c
=> straightforward - please apply
x86: fix Section mismatch warning in mcheck/mce_64.c
=> I took some assumptions on use of notifier.
See comments and please review before applying
x86: fix Section misma
s for the 3 above. However, the rcu code in -mm
> > is quite different, so the rcu patch may have a short life.
>
> Hi Randy.
>
> Thanks for your efforts!
And I just reviewd the three patches. All oops triggers under special
conditions.
It is stuff like this that ma
On Sat, Jan 19, 2008 at 11:52:55AM -0800, Randy Dunlap wrote:
> On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
>
> > kbuild emit section mismatch warnings when it detects that someone does a
> > call from a non-init section to a init section.
> > The rationale here
On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
> kbuild emit section mismatch warnings when it detects that someone does a
> call from a non-init section to a init section.
> The rationale here is that the init section are discarded at runtime and
> if this call happens af
On Thu, Jan 10, 2008 at 11:19:18AM -0800, Randy Dunlap wrote:
> On Wed, 9 Jan 2008 22:25:42 -0800 Randy Dunlap wrote:
>
> > On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
> >
> >
> > > This is the current list of warnings
> >
> > Sam,
> >
> > Several of these are due to driver variable
On Wed, Jan 09, 2008 at 10:25:42PM -0800, Randy Dunlap wrote:
> On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
>
>
> > This is the current list of warnings
>
> Sam,
>
> Several of these are due to driver variable names not matching
> the whitelisted names in modpost. I have patches for
On Wed, 9 Jan 2008 22:25:42 -0800 Randy Dunlap wrote:
> On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
>
>
> > This is the current list of warnings
>
> Sam,
>
> Several of these are due to driver variable names not matching
> the whitelisted names in modpost. I have patches for the one
On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
> This is the current list of warnings
Sam,
Several of these are due to driver variable names not matching
the whitelisted names in modpost. I have patches for the ones
that I have identified so far. And I have patches for a few of
the oth
kbuild emit section mismatch warnings when it detects that someone does a
call from a non-init section to a init section.
The rationale here is that the init section are discarded at runtime and
if this call happens after the init section has gone we have an oops.
This check is planned to be
Hello,
i get the following warnings when compiling 2.6.23-rc9.
.config attached.
MODPOST vmlinux.o
WARNING: vmlinux.o(.text+0x14): Section mismatch: reference
to .init.text:prom_init (between '__start' and '__after_mmu_off')
WARNING: vmlinux.o(.text+0x2c): Section mismatch: reference
to .init.tex
On Thu, Sep 13, 2007 at 10:35:05AM +0200, Frank van Maarseveen wrote:
> On Thu, Sep 13, 2007 at 09:02:00AM +0200, Sam Ravnborg wrote:
> > On Wed, Sep 12, 2007 at 06:00:17PM +0200, Frank van Maarseveen wrote:
> > > I'm still seeing the warnings below (2.6.22 started off with lots of
> > > section mi
On Thu, Sep 13, 2007 at 09:02:00AM +0200, Sam Ravnborg wrote:
> On Wed, Sep 12, 2007 at 06:00:17PM +0200, Frank van Maarseveen wrote:
> > I'm still seeing the warnings below (2.6.22 started off with lots of
> > section mismatch warning) but I have no idea if it is safe to ignore
> > these:
> >
> >
On Wed, Sep 12, 2007 at 06:00:17PM +0200, Frank van Maarseveen wrote:
> I'm still seeing the warnings below (2.6.22 started off with lots of
> section mismatch warning) but I have no idea if it is safe to ignore
> these:
>
> WARNING: arch/i386/kernel/built-in.o(.text+0xea62): Section mismatch:
>
I'm still seeing the warnings below (2.6.22 started off with lots of
section mismatch warning) but I have no idea if it is safe to ignore
these:
WARNING: arch/i386/kernel/built-in.o(.text+0xea62): Section mismatch: reference
to .init.data:trampoline_end (between 'setup_trampoline' and
'cpu_coreg
1 - 100 of 227 matches
Mail list logo
