The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Peter Teoh" <htmldeveloper@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Section mismatch: kernel/workqueue.c
Date: Mon, 4 Feb 2008 10:57:18 +0800	[thread overview]
Message-ID: <804dabb00802031857l73a02b87jcad9cc2a89d19f81@mail.gmail.com> (raw)

During compilation of the linus tree the following warnings are encountered:

WARNING: kernel/built-in.o(.data+0x2480): Section mismatch in
reference from the variable workqueue_cpu_callback_nb.14223 to the
function .devinit.text:workqueue_cpu_callback()
The variable workqueue_cpu_callback_nb.14223 references
the function __devinit workqueue_cpu_callback()
If the reference is valid then annotate the
variable with __init* (see linux/init.h) or name the variable:
*driver, *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,

This fix is to correct the following warning during compilation.
Based on my "elementary" analysis, as it is called from other
non-__init functions, this function cannot be declared as __devinit(),
correct?   Please comment.   Thanks :-).

Signed-off-by: Peter Teoh <htmldeveloper@gmail.com>

--- workqueue.c.orig    2008-02-04 10:47:03.000000000 +0800
+++ workqueue.c 2008-02-04 10:45:49.000000000 +0800
@@ -825,7 +825,7 @@ void destroy_workqueue(struct workqueue_
 }
 EXPORT_SYMBOL_GPL(destroy_workqueue);

-static int __devinit workqueue_cpu_callback(struct notifier_block *nfb,
+static int workqueue_cpu_callback(struct notifier_block *nfb,
                                                unsigned long action,
                                                void *hcpu)
 {

             reply	other threads:[~2008-02-04  2:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04  2:57 Peter Teoh [this message]
2008-02-04  5:55 ` Section mismatch: kernel/workqueue.c Sam Ravnborg

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=804dabb00802031857l73a02b87jcad9cc2a89d19f81@mail.gmail.com \
    --to=htmldeveloper@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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