From: Ralf Baechle <ralf@linux-mips.org>
To: James Hogan <james.hogan@imgtec.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Sanjay Lal <sanjayl@kymasys.com>,
kvm@vger.kernel.org, linux-mips@linux-mips.org,
linux-ia64@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: [PATCH -next] ia64, metag: Do not export min_low_pfn in arch-specific code
Date: Wed, 22 May 2013 17:57:17 +0000 [thread overview]
Message-ID: <20130522175717.GG10769@linux-mips.org> (raw)
In-Reply-To: <CAAG0J982gbca3XHHSpTHgqPgeGyJRtG8Lm1cWsT0HsThqdFeMw@mail.gmail.com>
On Sun, Apr 28, 2013 at 11:24:35AM +0100, James Hogan wrote:
> On 27 April 2013 19:20, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > As of commit 787dcbe6984b3638e94f60d807dcb51bb8a07211 ("MIPS: Export
> > symbols used by KVM/MIPS module"), min_low_pfn is already exported by
> > the generic mm/bootmem.c, causing:
> >
> > WARNING: vmlinux: 'min_low_pfn' exported twice. Previous export was in vmlinux
> >
> > Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
> This has been pointed out several times and needs fixing in the mips
> tree where the warning was introduced.
I've changed the MIPS code to no longer require the export of min_low_pfn
and dropped the export of that particular file. I still see that IA-64
and metag export min_low_pfn so maybe it should be exported from mm/
after all?
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@linux-mips.org>
To: James Hogan <james.hogan@imgtec.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Sanjay Lal <sanjayl@kymasys.com>,
kvm@vger.kernel.org, linux-mips@linux-mips.org,
linux-ia64@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: [PATCH -next] ia64, metag: Do not export min_low_pfn in arch-specific code
Date: Wed, 22 May 2013 19:57:17 +0200 [thread overview]
Message-ID: <20130522175717.GG10769@linux-mips.org> (raw)
In-Reply-To: <CAAG0J982gbca3XHHSpTHgqPgeGyJRtG8Lm1cWsT0HsThqdFeMw@mail.gmail.com>
On Sun, Apr 28, 2013 at 11:24:35AM +0100, James Hogan wrote:
> On 27 April 2013 19:20, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > As of commit 787dcbe6984b3638e94f60d807dcb51bb8a07211 ("MIPS: Export
> > symbols used by KVM/MIPS module"), min_low_pfn is already exported by
> > the generic mm/bootmem.c, causing:
> >
> > WARNING: vmlinux: 'min_low_pfn' exported twice. Previous export was in vmlinux
> >
> > Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
> This has been pointed out several times and needs fixing in the mips
> tree where the warning was introduced.
I've changed the MIPS code to no longer require the export of min_low_pfn
and dropped the export of that particular file. I still see that IA-64
and metag export min_low_pfn so maybe it should be exported from mm/
after all?
Ralf
next prev parent reply other threads:[~2013-05-22 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 18:20 [PATCH -next] ia64, metag: Do not export min_low_pfn in arch-specific code Geert Uytterhoeven
2013-04-27 18:20 ` Geert Uytterhoeven
2013-04-28 10:24 ` James Hogan
2013-04-28 10:24 ` James Hogan
2013-05-22 17:57 ` Ralf Baechle [this message]
2013-05-22 17:57 ` Ralf Baechle
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=20130522175717.GG10769@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=geert@linux-m68k.org \
--cc=james.hogan@imgtec.com \
--cc=kvm@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-next@vger.kernel.org \
--cc=sanjayl@kymasys.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 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.