From: Sam Ravnborg <sam@ravnborg.org>
To: Peter Teoh <htmldeveloper@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Coexistence of EXPORT_SYMBOL() and __cpuinit
Date: Mon, 4 Feb 2008 06:13:18 +0100 [thread overview]
Message-ID: <20080204051318.GA11255@uranus.ravnborg.org> (raw)
In-Reply-To: <804dabb00802031749m7f0765f8q8cd1f6c6a881651c@mail.gmail.com>
On Mon, Feb 04, 2008 at 09:49:24AM +0800, Peter Teoh wrote:
> In kernel/cpu.c, there exists API that is declared as __cpuinit, and
> at the same time exported via EXPORT_SYMBOL().
>
> Can these two attribute coexists at the same time? I mean, when it
> is declared with EXPORT_SYMBOL, according to include/linux/module.h,
> it is placed in a __ksymtab section, and when compiled with with
> __cpuinit, according to include/linux/init.h, into a __cpuinit
> section.
kbuild.git contains a commit so we no longer warn about
symbols being exported if annotatated with __cpuinit, __devinit, and
__devinit.
I've requested Linus to pull the changes and expet it to happen
within the next two days.
Sam
next prev parent reply other threads:[~2008-02-04 5:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 1:49 Peter Teoh
2008-02-04 5:13 ` Sam Ravnborg [this message]
2008-02-05 23:48 ` Randy Dunlap
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=20080204051318.GA11255@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=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
Powered by JetHome