From: Michael Ellerman <mpe@ellerman.id.au>
To: Masahiro Yamada <masahiroy@kernel.org>,
Joel Stanley <joel@jms.id.au>,
linuxppc-dev@lists.ozlabs.org
Cc: Nicolas Schier <nicolas@fjasle.eu>,
linux-kbuild@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH] powerpc: remove checks for binutils older than 2.25
Date: Tue, 27 Jun 2023 21:58:39 +1000 [thread overview]
Message-ID: <87h6qtglqo.fsf@mail.lhotse> (raw)
In-Reply-To: <CAK7LNAS=UCo_o-B0mgsR+SDb0sYwvQo90uag5sJ1UmB+8NqLjQ@mail.gmail.com>
Masahiro Yamada <masahiroy@kernel.org> writes:
> On Thu, Jan 19, 2023 at 9:37 PM Masahiro Yamada <masahiroy@kernel.org> wrote:
>>
>> On Thu, Jan 19, 2023 at 9:12 PM Joel Stanley <joel@jms.id.au> wrote:
>> >
>> > On Thu, 19 Jan 2023 at 08:24, Masahiro Yamada <masahiroy@kernel.org> wrote:
>> > >
>> > > Commit e4412739472b ("Documentation: raise minimum supported version of
>> > > binutils to 2.25") allows us to remove the checks for old binutils.
>> > >
>> > > There is no more user for ld-ifversion. Remove it as well.
>> >
>> > ppc kernels fail to link with 2.27 under some configurations:
>> >
>> > https://github.com/linuxppc/issues/issues/388
>> >
>> > We may want to use ld-ifversion to exclude that version.
>>
>
> Ping?
Sorry. I've now applied the binutils 2.27 patch from Naveen, and this on
top with minor tweaks to make it apply. The result is in my next branch.
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next
cheers
next prev parent reply other threads:[~2023-06-27 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 8:22 [PATCH] powerpc: remove checks for binutils older than 2.25 Masahiro Yamada
2023-01-19 12:12 ` Joel Stanley
2023-01-19 12:37 ` Masahiro Yamada
2023-06-25 8:02 ` Masahiro Yamada
2023-06-26 1:58 ` Nicholas Piggin
2023-06-26 3:11 ` Masahiro Yamada
2023-06-26 4:41 ` Nicholas Piggin
2023-06-27 11:58 ` Michael Ellerman [this message]
2023-07-03 5:26 ` Michael Ellerman
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=87h6qtglqo.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=joel@jms.id.au \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--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;
as well as URLs for NNTP newsgroup(s).