mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
	David Miller <davem@davemloft.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 4.18-rc6
Date: Tue, 24 Jul 2018 08:18:45 +0200	[thread overview]
Message-ID: <20180724081845.1cc4c9d8@mschwideX1> (raw)
In-Reply-To: <CA+55aFw3tRe70mUgV70oi6xBwSLx0h_supRGoNUHgrcSGxUgeg@mail.gmail.com>

On Mon, 23 Jul 2018 16:17:22 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck <linux@roeck-us.net> wrote:
> >  
> > >
> > > Martin - can we just remove the
> > >
> > >          select HAVE_GCC_PLUGINS
> > >
> > > from the s390 Kconfig file (or perhaps add "if BROKEN" or something to
> > > disable it).
> > >
> > > Because if it's not getting fixed, it shouldn't be exposed.
> > >  
> > The problem only affects 4.18 - the code has been rearranged in -next.
> > Only, in my builders, I can't disable a flag for individual releases,
> > so I just disabled it completely for s390.  
> 
> Well, I'm not going to release a 4.18 with a known problem, so in 4.18
> this *will* be disabled if it's not fixed.
> 
> The fact that it might be fixed in linux-next is entirely immaterial
> to the release of 4.18.

Ok, if gcc with the plugins and an allmodconfig is considered to be
important enough to warrant a fix, it can be pulled from here:

git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus

Martin Schwidefsky (1):
      s390: disable gcc plugins

Once that is in I will create another patch to undo this one and place
it after the early boot rework.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.


  reply	other threads:[~2018-07-24  6:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-22 21:23 Linus Torvalds
2018-07-23 20:46 ` Guenter Roeck
2018-07-23 20:56   ` Linus Torvalds
2018-07-23 21:06     ` David Miller
2018-07-23 21:23     ` Guenter Roeck
2018-07-23 23:16       ` Linus Torvalds
2018-07-23 23:17       ` Linus Torvalds
2018-07-24  6:18         ` Martin Schwidefsky [this message]
2018-07-24  7:15           ` Christian Borntraeger
2018-07-24  7:24             ` Martin Schwidefsky
2018-07-24  7:28               ` Christian Borntraeger
2018-07-25 19:40               ` Kees Cook
2018-07-26  6:00                 ` Martin Schwidefsky

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=20180724081845.1cc4c9d8@mschwideX1 \
    --to=schwidefsky@de.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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

Powered by JetHome