From: Adam Borowski <kilobyte@angband.pl>
To: Michal Marek <mmarek@suse.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] kbuild post v4.9-rc1 fixes
Date: Sun, 20 Nov 2016 20:11:43 +0100 [thread overview]
Message-ID: <20161120191143.GA29543@angband.pl> (raw)
In-Reply-To: <20161118205051.GA11224@sepie.suse.cz>
On Fri, Nov 18, 2016 at 09:50:51PM +0100, Michal Marek wrote:
> Hi Linus,
>
> Here are some regression fixes for kbuild:
> - modversion support for exported asm symbols (Nick Piggin). The
> affected architectures need separate patches adding asm-prototypes.h.
As the pull request's comment says, we do need the per-arch asm-prototypes.h
patches. I've just checked on x86: still broken with current mainline,
works with my patch from 20161102121427.10103-1-kilobyte@angband.pl;
I suspect the arm counterpart (patch by Arnd Bergmann) is also needed
(you just commented on that thread).
--
A true bird-watcher waves his tail while doing so.
prev parent reply other threads:[~2016-11-20 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 20:50 [GIT PULL] kbuild post v4.9-rc1 fixes Michal Marek
2016-11-20 19:11 ` Adam Borowski [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=20161120191143.GA29543@angband.pl \
--to=kilobyte@angband.pl \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=torvalds@linux-foundation.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