From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Nicholas Piggin <npiggin@gmail.com>,
Michal Marek <mmarek@suse.cz>
Subject: Re: linux-next: Tree for Dec 1
Date: Fri, 2 Dec 2016 07:23:02 +1100 [thread overview]
Message-ID: <20161202072302.3b127688@canb.auug.org.au> (raw)
In-Reply-To: <c8120142-ec74-c866-f1b2-cafc3d109574@infradead.org>
Hi Randy,
On Thu, 1 Dec 2016 12:17:30 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> on i386:
>
> WARNING: EXPORT symbol "__sw_hweight32" [arch/x86/lib/built-in.ko] version generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "___preempt_schedule" [arch/x86/entry/built-in.ko] version generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "___preempt_schedule" [arch/x86/built-in.ko] version generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "___preempt_schedule" [vmlinux] version generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "__put_user_2" [vmlinux] version generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "__get_user_2" [vmlinux] version generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "__put_user_1" [vmlinux] version generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "__get_user_1" [vmlinux] version generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "__sw_hweight32" [vmlinux] version generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "empty_zero_page" [vmlinux] version generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "__put_user_8" [vmlinux] version generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "__put_user_4" [vmlinux] version generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "__get_user_4" [vmlinux] version generation failed, symbol will not be versioned.
>
> Do I have a tools problem?
No, these are existing problems that are now complained about. Nick
Piggin hopes to get rid of these warnings for 3.10.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-12-01 20:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 6:42 linux-next: Tree for Dec 1 Stephen Rothwell
2016-12-01 18:38 ` linux-next: Tree for Dec 1 (ethernet/mellanox) Randy Dunlap
2016-12-01 20:17 ` linux-next: Tree for Dec 1 Randy Dunlap
2016-12-01 20:23 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-01 2:37 Stephen Rothwell
2022-12-01 4:49 Stephen Rothwell
2021-12-01 5:37 Stephen Rothwell
2020-12-01 10:03 Stephen Rothwell
2017-12-01 2:53 Stephen Rothwell
2014-12-01 10:10 Stephen Rothwell
2011-12-01 4:53 Stephen Rothwell
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=20161202072302.3b127688@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=npiggin@gmail.com \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).