From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: Guenter Roeck Date: Tue, 11 Sep 2018 10:27:41 -0700 From: Guenter Roeck To: Geert Uytterhoeven Message-ID: <20180911172741.GA2767@roeck-us.net> References: <20180910220208.GB17966@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Cc: Ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Deprecation / Removal of old hardware support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Geert, On Tue, Sep 11, 2018 at 10:49:25AM +0200, Geert Uytterhoeven wrote: > Hi Günter, > > On Tue, Sep 11, 2018 at 12:02 AM Guenter Roeck wrote: > > On Mon, Sep 10, 2018 at 11:40:59PM +0200, Arnd Bergmann wrote: > > > One architecture (unicore32) got saved in the last minute by > > > the maintainer saying that he'd rather keep it in tree, despite not > > > even having a publicly available toolchain with sources. > > > > unicore32 no longer builds with the mainline kernel because the > > (private) toolchain is too old (gcc < 4.6), so it may be time > > to revisit that decision. > > I'm still building mainline with gcc-4.1.2, using: > > git revert 815f0ddb346c1960 # "include/linux/compiler*.h: make > compiler-*.h mutually exclusive" > git revert cafa0010cd51fb71 # "Raise the minimum required gcc > version to 4.6" > > leading to one recent bug fix: > > https://lore.kernel.org/lkml/20180823212738.18431-1-geert@linux-m68k.org/ > > and two code improvements: > > https://lore.kernel.org/lkml/20180823212436.17423-1-geert@linux-m68k.org/ > https://lore.kernel.org/lkml/20180823213027.18856-1-geert@linux-m68k.org/ > Interesting. How to you manage to not hit the problem reported with https://lkml.org/lkml/2018/8/14/472 ? Thanks, Guenter