From: Adrian Bunk <bunk@stusta.de>
To: dbrownell@users.sourceforge.net
Cc: spi-devel-general@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [2.6 patch] spi.c:scan_boardinfo() mustn't be __init_or_module
Date: Tue, 10 Jul 2007 14:44:42 +0200 [thread overview]
Message-ID: <20070710124442.GV3492@stusta.de> (raw)
This patch fixes the following section mismatch:
<-- snip -->
...
MODPOST vmlinux
WARNING: drivers/built-in.o(.text+0x889735): Section mismatch: reference to .init.text:scan_boardinfo (between 'spi_register_master' and '__unregister')
...
<-- snip -->
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
--- linux-2.6.22-rc6-mm1/drivers/spi/spi.c.old 2007-07-10 04:17:26.000000000 +0200
+++ linux-2.6.22-rc6-mm1/drivers/spi/spi.c 2007-07-10 04:18:01.000000000 +0200
@@ -302,8 +302,7 @@
* creates board info from kernel command lines
*/
-static void __init_or_module
-scan_boardinfo(struct spi_master *master)
+static void scan_boardinfo(struct spi_master *master)
{
struct boardinfo *bi;
struct device *dev = master->cdev.dev;
next reply other threads:[~2007-07-10 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 12:44 Adrian Bunk [this message]
2007-07-10 16:54 ` [2.6 patch] spi.c:scan_boardinfo() mustn't be __init_or_module David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070710124442.GV3492@stusta.de \
--to=bunk@stusta.de \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox