From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Segher Boessenkool <segher@kernel.crashing.org>,
Joel Stanley <joel@jms.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: vmlinux.lds: Drop Binutils 2.18 workarounds
Date: Thu, 28 Mar 2019 07:19:57 +0100 [thread overview]
Message-ID: <4ceb12ff-b114-6edd-e9c2-a6cd922720a2@c-s.fr> (raw)
In-Reply-To: <20190327182128.GA3969@gate.crashing.org>
Le 27/03/2019 à 19:21, Segher Boessenkool a écrit :
> On Wed, Mar 27, 2019 at 07:47:55AM -0500, Segher Boessenkool wrote:
>> On Wed, Mar 27, 2019 at 07:40:32AM +0100, Christophe Leroy wrote:
>>> Le 26/03/2019 à 23:29, Segher Boessenkool a écrit :
>>>> I tried to reproduce this. It does not fail with a ppc6xx_defconfig
>>>> build, and mpc885_ads_defconfig fails with
>>>
>>> So far, the only defconfig which fails for me is ppc64_defconfig, like
>>> Michael.
>>
>> Oh, I misunderstood then. Let me try that :-)
>
> Yeah, okay, we should have some PHDRS statement here still. You can drop
> the dummy segment, and the notes segment as well, or you can keep the notes
> section in both the notes and kernel segments.
Is the note segment useful at all ? I guess if we decide to keep it, we
should have a reason.
>
> (You patch doesn't apply btw, whitespace damage I think; will you send a
> new one?)
Originally the patch is by Joel Stanley <joel@jms.id.au>
I guess he will send a v2 taking into account the discussion ?
Or maybe you can send it yourself as you are probably the best person to
explain in details the change in the commit message.
Christophe
next prev parent reply other threads:[~2019-03-28 6:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 0:32 [PATCH] powerpc: vmlinux.lds: Drop Binutils 2.18 workarounds Joel Stanley
2019-03-21 23:34 ` Segher Boessenkool
2019-03-22 0:22 ` Michael Ellerman
2019-03-26 0:55 ` Michael Ellerman
2019-03-26 7:55 ` Christophe Leroy
2019-03-26 18:19 ` Segher Boessenkool
2019-03-26 19:28 ` Christophe Leroy
2019-03-26 20:12 ` Segher Boessenkool
2019-03-26 22:29 ` Segher Boessenkool
2019-03-26 22:59 ` Segher Boessenkool
2019-03-27 6:40 ` Christophe Leroy
2019-03-27 12:47 ` Segher Boessenkool
2019-03-27 18:21 ` Segher Boessenkool
2019-03-28 6:19 ` Christophe Leroy [this message]
2019-03-28 15:11 ` Segher Boessenkool
2019-03-27 8:56 ` Christophe Leroy
2019-03-27 9:09 ` Christophe Leroy
2019-03-26 8:08 ` Christophe Leroy
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=4ceb12ff-b114-6edd-e9c2-a6cd922720a2@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=segher@kernel.crashing.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).