linux-kernel - section mismatches with _sm501_register_gpio() and _sm501_gpio_register

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <8bd0f97a0811202013r170c9906i15797ca953844cff@mail.gmail.com>
Date:	Thu, 20 Nov 2008 23:13:31 -0500
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	ben@...tec.co.uk, sameo@...nedhand.com
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: section mismatches with _sm501_register_gpio() and _sm501_gpio_register_chip()

WARNING: drivers/mfd/built-in.o(.text+0x8d6): Section mismatch in
reference from the function _sm501_register_gpio() to the function
.devinit.text:_sm501_gpio_register_chip()
The function _sm501_register_gpio() references
the function __devinit _sm501_gpio_register_chip().
This is often because _sm501_register_gpio lacks a __devinit
annotation or the annotation of _sm501_gpio_register_chip is wrong.

WARNING: drivers/mfd/built-in.o(.text+0x90a): Section mismatch in
reference from the function _sm501_register_gpio() to the function
.devinit.text:_sm501_gpio_register_chip()
The function _sm501_register_gpio() references
the function __devinit _sm501_gpio_register_chip().
This is often because _sm501_register_gpio lacks a __devinit
annotation or the annotation of _sm501_gpio_register_chip is wrong.

#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
CONFIG_MFD_SM501=y
CONFIG_MFD_SM501_GPIO=y
CONFIG_HTC_PASIC3=y
CONFIG_UCB1400_CORE=m
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_WM8400 is not set
CONFIG_MFD_WM8350=y
CONFIG_MFD_WM8350_I2C=y
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/