From: Andrew Morton <akpm@osdl.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: kwin@ns.sympatico.ca, ak@muc.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm3] x86-64: Eliminate register_die_notifier symbol exported twice
Date: Thu, 9 Mar 2006 17:37:38 -0800 [thread overview]
Message-ID: <20060309173738.6a97d0eb.akpm@osdl.org> (raw)
In-Reply-To: <20060309172854.ae8eeec9.rdunlap@xenotime.net>
"Randy.Dunlap" <rdunlap@xenotime.net> wrote:
>
> On Thu, 09 Mar 2006 19:44:59 -0400 Kevin Winchester wrote:
>
> >
> > register_die_notifier is exported twice, once in traps.c and once in
> > x8664_ksyms.c. This results in a warning on build.
> >
> > Signed-Off-By: Kevin Winchester <kwin@ns.sympatico.ca>
> >
> > --- v2.6.16-rc5-mm3.orig/arch/x86_64/kernel/x8664_ksyms.c
> > 2006-03-09 19:34:11.000000000 -0400
> > +++ v2.6.16-rc5-mm3/arch/x86_64/kernel/x8664_ksyms.c 2006-03-09
> > 19:40:46.000000000 -0400
> > @@ -142,7 +142,6 @@ EXPORT_SYMBOL(rwsem_down_write_failed_th
> > EXPORT_SYMBOL(empty_zero_page);
> >
> > EXPORT_SYMBOL(die_chain);
> > -EXPORT_SYMBOL(register_die_notifier);
> >
> > #ifdef CONFIG_SMP
> > EXPORT_SYMBOL(cpu_sibling_map);
>
> Thanks for that. However, I see 2 such warnings:
>
> WARNING: vmlinux: 'register_die_notifier' exported twice. Previous export was in vmlinux
> WARNING: vmlinux: 'strlen' exported twice. Previous export was in vmlinux
>
They're all over the place. Some of them are due to -mm-only patches.
It's not very urgent. Let's get Sam's stuff settled down into mainline and
get all such warnings in mainline fixed up first. That way, people will
then know when their new patches are being bad and I'll know when -mm
patches need fixups.
next prev parent reply other threads:[~2006-03-10 1:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 23:44 [PATCH -mm3] x86-64: Eliminate register_die_notifier symbol exported twice Kevin Winchester
2006-03-09 17:48 ` Andi Kleen
2006-03-10 1:28 ` Randy.Dunlap
2006-03-10 1:37 ` Andrew Morton [this message]
2006-03-10 12:29 ` Kevin Winchester
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=20060309173738.6a97d0eb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@muc.de \
--cc=kwin@ns.sympatico.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.