From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Peter Zijlstra <peterz@infradead.org>
Cc: syzbot <syzbot+dbf8cf3717c8ef4a90a0@syzkaller.appspotmail.com>,
bp@alien8.de, hpa@zytor.com, jmattson@google.com,
joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
mingo@redhat.com, pbonzini@redhat.com,
sean.j.christopherson@intel.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, vkuznets@redhat.com, wanpengli@tencent.com,
x86@kernel.org, elver@google.com
Subject: Re: linux-next build error (9)
Date: Tue, 23 Jun 2020 20:17:30 +1000 [thread overview]
Message-ID: <20200623201730.6c085687@canb.auug.org.au> (raw)
In-Reply-To: <20200623093230.GD4781@hirez.programming.kicks-ass.net>
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
Hi Peter,
On Tue, 23 Jun 2020 11:32:30 +0200 Peter Zijlstra <peterz@infradead.org> wrote:
>
> I suppose the next quest is finding a s390 compiler version that works
> and then bumping the version test in the aforementioned commit.
Not a lot of help, but my Debian cross compiler seems to work:
$ s390x-linux-gnu-gcc --version
s390x-linux-gnu-gcc (Debian 9.3.0-13) 9.3.0
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-23 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 9:37 linux-next build error (9) syzbot
2020-06-22 9:49 ` Peter Zijlstra
2020-06-22 11:06 ` Marco Elver
2020-06-22 13:12 ` Marco Elver
2020-06-23 2:44 ` Stephen Rothwell
2020-06-23 9:32 ` Peter Zijlstra
2020-06-23 10:09 ` Marco Elver
2020-06-23 10:17 ` Stephen Rothwell [this message]
2020-06-23 11:24 ` Marco Elver
2020-06-23 23:00 ` Stephen Rothwell
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=20200623201730.6c085687@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bp@alien8.de \
--cc=elver@google.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=sean.j.christopherson@intel.com \
--cc=syzbot+dbf8cf3717c8ef4a90a0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).