From: Adam Borowski <kilobyte@angband.pl>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Borislav Petkov <bp@alien8.de>, Al Viro <viro@zeniv.linux.org.uk>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 784d5699eddc ("x86: move exports to actual definitions")
Date: Wed, 19 Oct 2016 02:10:04 +0200 [thread overview]
Message-ID: <20161019001004.GA27544@angband.pl> (raw)
In-Reply-To: <20161018202915.GA307@x4>
On Tue, Oct 18, 2016 at 10:29:15PM +0200, Markus Trippelsdorf wrote:
> On 2016.10.18 at 22:23 +0200, Borislav Petkov wrote:
> > I see the gazillion warnings below when building -rc1 here.
> >
> > When I revert
> >
> > 784d5699eddc ("x86: move exports to actual definitions")
> >
> > the warnings are gone.
Already being fixed, please take a look at the thread starting at
20161016002205.GA9686@vader; for your convenience I've put Nicholas Piggin's
initial work, my lousy but works-for-me fix for x86, Arnd Bergmann's for arm
at git@github.com:kilobyte/linux.git branch kbuild-exports.
> I'm seeing the same thing on ppc64le with an allmodconfig.
I guess ppc64 needs a similar patch.
Meow!
--
A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
raspberries, 0.4kg sugar; put into a big jar for 1 month. Filter out and
throw away the fruits (can dump them into a cake, etc), let the drink age
at least 3-6 months.
next prev parent reply other threads:[~2016-10-19 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 20:23 784d5699eddc ("x86: move exports to actual definitions") Borislav Petkov
2016-10-18 20:29 ` Markus Trippelsdorf
2016-10-18 20:40 ` Markus Trippelsdorf
2016-10-19 0:10 ` Adam Borowski [this message]
2016-10-19 10:23 ` Borislav Petkov
2016-10-19 13:45 ` Steven Rostedt
2016-10-20 21:07 ` Gabriel C
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=20161019001004.GA27544@angband.pl \
--to=kilobyte@angband.pl \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=viro@zeniv.linux.org.uk \
/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.