From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 4.19-rc1
Date: Tue, 28 Aug 2018 09:01:34 -0700 [thread overview]
Message-ID: <20180828160134.GA17166@roeck-us.net> (raw)
In-Reply-To: <CA+55aFwO72FivHHBdVky96wSgESNZza4A_g2QsovWfgxf7qH=g@mail.gmail.com>
On Mon, Aug 27, 2018 at 02:56:32PM -0700, Linus Torvalds wrote:
> On Mon, Aug 27, 2018 at 6:45 AM Guenter Roeck <linux@roeck-us.net> wrote:
> >
> > Build results:
> > total: 132 pass: 129 fail: 3
>
> Thanks for running these. Looks like everything but the sparc thing is
> under control, and the sparc thing might be one of those "big builds
> don't work on sparc" ;(
>
In general I would agree. On the other side, someone who knows sparc
assembler should be able to fix the problem. sparc is notorious for
failing allmodconfig builds, mostly due to its separate devicetree
implementation. On top of that, many allmodconfig builds already fail,
often for minor reasons such as duplicate symbols or missing exports.
Dropping sparc:allmodconfig will cause sparc builds to deteriorate,
and we'll lose valuable build feedback. On the plus side,
sparc64:allmodconfig still builds, but that doesn't cover 32/64 bit
differences.
I'll monitor the situation for a while and stop building sparc:allmodconfig
if the problem isn't fixed around -rc7.
Guenter
next prev parent reply other threads:[~2018-08-28 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 21:49 Linux 4.19-rc1 Linus Torvalds
2018-08-27 1:39 ` linux-next: stats (Was: Linux 4.19-rc1) Stephen Rothwell
2018-08-27 13:44 ` Linux 4.19-rc1 Guenter Roeck
2018-08-27 15:46 ` Christoph Hellwig
2018-08-27 17:11 ` Guenter Roeck
2018-08-27 18:13 ` Christoph Hellwig
2018-08-27 19:32 ` Guenter Roeck
2018-08-27 21:32 ` Palmer Dabbelt
2018-08-27 21:56 ` Linus Torvalds
2018-08-28 16:01 ` Guenter Roeck [this message]
2018-08-27 19:10 ` Shuah Khan
2018-08-27 20:25 ` Winkler, Tomas
2018-08-29 9:56 ` David Laight
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=20180828160134.GA17166@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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