From: Michal Marek <mmarek@suse.com>
To: Guenter Roeck <linux@roeck-us.net>, Nicholas Piggin <npiggin@gmail.com>
Cc: Chen Liqin <liqin.linux@gmail.com>,
Lennox Wu <lennox.wu@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Build failure in -next due to 'kbuild: allow archs to select link dead code/data elimination'
Date: Thu, 22 Sep 2016 14:38:18 +0200 [thread overview]
Message-ID: <a9ee7dd2-2b0f-37a2-3351-832a06bff6c7@suse.com> (raw)
In-Reply-To: <20160914194853.GB16397@roeck-us.net>
On 2016-09-14 21:48, Guenter Roeck wrote:
> On Wed, Sep 14, 2016 at 12:30:04PM +1000, Nicholas Piggin wrote:
>> commit 0ae28be83b4d6cd03ef5b481487d042f2b91954e
>> Author: Nicholas Piggin <npiggin@gmail.com>
>> Date: Wed Sep 14 12:24:03 2016 +1000
>>
>> kbuild: -ffunction-sections fix for archs with conflicting sections
>>
>> Enabling -ffunction-sections modified the generic linker script to
>> pull .text.* sections into regular TEXT_TEXT section, conflicting
>> with some architectures. Revert that change and require archs that
>> enable the option to ensure they have no conflicting section names,
>> and do the appropriate merging.
>>
>> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
>>
> Tested-by: Guenter Roeck <linux@roeck-us.net>
Applied to kbuild.git#kbuild.
Thanks,
Michal
prev parent reply other threads:[~2016-09-22 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 22:24 Guenter Roeck
2016-09-13 2:00 ` Nicholas Piggin
2016-09-13 3:17 ` Guenter Roeck
2016-09-13 3:51 ` Nicholas Piggin
2016-09-13 20:25 ` Guenter Roeck
2016-09-14 2:30 ` Nicholas Piggin
2016-09-14 19:48 ` Guenter Roeck
2016-09-22 12:38 ` Michal Marek [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=a9ee7dd2-2b0f-37a2-3351-832a06bff6c7@suse.com \
--to=mmarek@suse.com \
--cc=lennox.wu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=liqin.linux@gmail.com \
--cc=npiggin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®