From: Michael Ellerman <mpe@ellerman.id.au>
To: Helge Deller <deller@gmx.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: Build regressions/improvements in v4.18-rc3
Date: Wed, 04 Jul 2018 14:59:18 +1000 [thread overview]
Message-ID: <87po03lhp5.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <b7c41645-f694-4763-4cc3-f7abb0c2432b@gmx.de>
Helge Deller <deller@gmx.de> writes:
> On 03.07.2018 03:09, Michael Ellerman wrote:
>> Helge Deller <deller@gmx.de> writes:
>>
>>> On 02.07.2018 16:09, Geert Uytterhoeven wrote:
>>>> On Mon, Jul 2, 2018 at 4:01 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>>>>> JFYI, when comparing v4.18-rc3[1] to v4.18-rc2[3], the summaries are:
>>>> ...
>>>
>>> Both of the following are simply happening because of old compiler which is being used:
>>>
>>>>> [Deleted 26903 lines about "warning: ... [-Wpointer-sign]" on parisc-allmodconfig]
>>
>> It's GCC 4.6.3. Are you saying that's not supported anymore?
>>
>> I can update to 8.1.0 if that's more useful.
>
> Yes, please.
> Any version >= 7.2.1 should be better.
OK, done. It's now using 8.1.0 from kernel.org.
Do you want kisskb to email you build failures for parsic in linux-next
and/or Linus' tree?
It only mails when a config goes from working to broken or vice versa,
so shouldn't be too chatty.
cheers
next prev parent reply other threads:[~2018-07-04 4:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 14:00 Geert Uytterhoeven
2018-07-02 14:09 ` Geert Uytterhoeven
2018-07-02 15:13 ` Helge Deller
2018-07-03 1:09 ` Michael Ellerman
2018-07-03 6:18 ` Helge Deller
2018-07-04 4:59 ` Michael Ellerman [this message]
2018-07-03 13:22 ` John David Anglin
2018-07-04 4:56 ` 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=87po03lhp5.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.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
all inboxes | Powered by JetHome®