From: James Hogan <james.hogan@imgtec.com>
To: Tony Luck <tony.luck@intel.com>
Cc: Sanjay Lal <sanjayl@kymasys.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-next@vger.kernel.org
Subject: Re: EXPORT_SYMBOL(min_low_pfn);
Date: Wed, 6 Feb 2013 09:40:01 +0000 [thread overview]
Message-ID: <511224F1.7020806@imgtec.com> (raw)
In-Reply-To: <CA+8MBbLW333z1Subx=fLu46u2RQXkNB1iTbORuKbq7YpZi1X_w@mail.gmail.com>
On 05/02/13 19:31, Tony Luck wrote:
> Today i noticed in linux-next this commit:
>
> commit b0d9c17503444c2df8cb8e93ccfa4877edd71933
> Author: Sanjay Lal <sanjayl@kymasys.com>
> Date: Wed Nov 21 18:34:14 2012 -0800
>
> MIPS: Export symbols used by KVM/MIPS module
>
> which causes this kernel build warning on ia64:
>
> WARNING: vmlinux: 'min_low_pfn' exported twice. Previous export was in vmlinux
>
>
> We just need to delete the arch/ia64 specific export (and grep says
> for arch/metag too):
>
> $ git grep min_low_pfn | grep EXPORT
> arch/ia64/kernel/ia64_ksyms.c:EXPORT_SYMBOL(min_low_pfn); /* defined
> by bootmem.c, but not exported by generic code */
> arch/metag/kernel/metag_ksyms.c:EXPORT_SYMBOL(min_low_pfn);
> mm/bootmem.c:EXPORT_SYMBOL(min_low_pfn);
Yes, I had noticed this the other day too. I'll probably roll the
equivalent metag patch into the metag tree since on metag it does no
real harm not exporting it at this stage.
Cheers
James
prev parent reply other threads:[~2013-02-06 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 19:31 EXPORT_SYMBOL(min_low_pfn); Tony Luck
2013-02-06 0:36 ` EXPORT_SYMBOL(min_low_pfn); Stephen Rothwell
2013-03-14 11:38 ` EXPORT_SYMBOL(min_low_pfn); James Hogan
2013-02-06 9:40 ` James Hogan [this message]
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=511224F1.7020806@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=linux-next@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=sanjayl@kymasys.com \
--cc=tony.luck@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).