From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Deprecation / Removal of old hardware support
Date: Tue, 11 Sep 2018 11:27:06 -0700 [thread overview]
Message-ID: <20180911182706.GB21160@roeck-us.net> (raw)
In-Reply-To: <CAMuHMdU-M7zBbQ-BBu6gF=6X+TnX9y207ADzKJ1i+VanxRFCdQ@mail.gmail.com>
On Tue, Sep 11, 2018 at 07:58:48PM +0200, Geert Uytterhoeven wrote:
> Hi Günter,
>
> On Tue, Sep 11, 2018 at 7:27 PM Guenter Roeck <linux@roeck-us.net> wrote:
> > On Tue, Sep 11, 2018 at 10:49:25AM +0200, Geert Uytterhoeven wrote:
> > > On Tue, Sep 11, 2018 at 12:02 AM Guenter Roeck <linux@roeck-us.net> 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 ?
>
> Sorry, I forgot I have also applied Andrew's wibble patch:
> https://lore.kernel.org/lkml/20180814160208.4f4dd7ca142912f5894ddddd@linux-foundation.org/
>
Hmm. I don't really want to have to maintain a set of patches on top upstream
and stable kernels to be able to run my tests. I do have a set of configuration
options to apply, but anything beyond that is, in my opinion, out of scope
for (at least my) testing.
Thanks,
Guenter
next prev parent reply other threads:[~2018-09-11 18:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 14:04 Peter Huewe
2018-09-10 15:31 ` Linus Walleij
2018-09-10 21:40 ` Arnd Bergmann
2018-09-10 22:02 ` Guenter Roeck
2018-09-11 8:49 ` Geert Uytterhoeven
2018-09-11 17:27 ` Guenter Roeck
2018-09-11 17:58 ` Geert Uytterhoeven
2018-09-11 18:27 ` Guenter Roeck [this message]
2018-09-11 18:37 ` Daniel Vetter
2018-09-11 8:37 ` Linus Walleij
2018-09-11 9:37 ` Lukasz Majewski
2018-09-11 19:33 ` Greg KH
2018-09-11 21:39 ` Laurent Pinchart
2018-09-11 21:50 ` Thomas Gleixner
2018-09-12 6:40 ` Geert Uytterhoeven
2018-09-12 10:23 ` Arnd Bergmann
2018-09-12 6:26 ` Greg KH
2018-09-12 6:49 ` Peter Huewe
2018-09-12 7:07 ` Greg KH
2018-09-11 10:52 ` Mark Brown
2018-09-11 11:22 ` Linus Walleij
[not found] ` <TY2PR0101MB2526376DEFC241B754A19A6AE21C0@TY2PR0101MB2526.apcprd01.prod.exchangelabs.com>
2018-09-27 15:25 ` SZ Lin (林上智)
2018-09-28 10:45 ` Thomas Gleixner
2018-09-11 11:53 ` Arnd Bergmann
2018-09-11 21:28 ` Alexander Sverdlin
2018-09-11 21:16 ` Alexander Sverdlin
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=20180911182706.GB21160@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Ksummit-discuss@lists.linuxfoundation.org \
--cc=geert@linux-m68k.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