Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 28 Aug 2018 09:01:34 -0700
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
Message-ID: <20180828160134.GA17166@roeck-us.net>
References: <CA+55aFw9mxNPX6OtOp-aoUMdXSg=gBkQudGGamo__sh_ts_LdQ@mail.gmail.com>
 <20180827134459.GA16094@roeck-us.net>
 <CA+55aFwO72FivHHBdVky96wSgESNZza4A_g2QsovWfgxf7qH=g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+55aFwO72FivHHBdVky96wSgESNZza4A_g2QsovWfgxf7qH=g@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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