| 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
| ||
|
Date: Thu, 18 Dec 2008 15:56:53 -0500 From: "Mike Frysinger" <vapier.adi@...il.com> To: "Samuel Ortiz" <sameo@...nedhand.com> Cc: ben@...tec.co.uk, LKML <linux-kernel@...r.kernel.org> Subject: Re: section mismatches with _sm501_register_gpio() and _sm501_gpio_register_chip() On Mon, Nov 24, 2008 at 14:49, Samuel Ortiz wrote: > On Thu, Nov 20, 2008 at 11:13:31PM -0500, Mike Frysinger wrote: >> 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. > > Which kernel are you triggering this on ? sorry, i missed this response ... this was in 2.6.28-rc2 -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/
Powered by blists - more mailing lists