From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Matthias Kaehlcke <mka@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/build changes for v4.17
Date: Tue, 3 Apr 2018 14:09:21 +0200 [thread overview]
Message-ID: <20180403120921.GC4082@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180403095118.rpf7tj577dppvx7d@gmail.com>
On Tue, Apr 03, 2018 at 11:51:18AM +0200, Ingo Molnar wrote:
> If it's being relied on, or if there's actually something firmly planned,
> which we could track, then I'd have no problem with reverting this change
> and waiting one more kernel cycle or so.
I don't see why the clang people can't go back to using out of tree
patches to make their compile 'work' until they've caught up with 7-year
old tech.
Also, I'd really like to know if there are any plans to support
asm-cc-output, otherwise we'll have this same old drama all over again
in a few years :/
next prev parent reply other threads:[~2018-04-03 12:09 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 9:50 [GIT PULL] x86/build changes for v4.17 Ingo Molnar
2018-04-02 21:44 ` Linus Torvalds
2018-04-02 22:38 ` Matthias Kaehlcke
2018-04-03 1:26 ` Matthias Kaehlcke
2018-04-03 8:59 ` Peter Zijlstra
2018-04-03 9:51 ` Ingo Molnar
2018-04-03 12:09 ` Peter Zijlstra [this message]
2018-04-03 18:06 ` Matthias Kaehlcke
2018-04-03 21:58 ` Nick Desaulniers
2018-04-04 9:19 ` Peter Zijlstra
2018-04-04 9:38 ` Greg KH
2018-04-04 16:49 ` Nick Desaulniers
2018-04-04 17:13 ` Linus Torvalds
2018-04-04 17:46 ` Nick Desaulniers
2018-04-04 23:10 ` Nick Desaulniers
2018-04-04 16:53 ` Nick Desaulniers
2018-04-04 16:59 ` Greg KH
2018-04-04 19:26 ` James Y Knight
2018-04-04 19:42 ` Linus Torvalds
2018-04-04 22:21 ` James Y Knight
2018-04-04 22:29 ` Linus Torvalds
2018-04-05 7:08 ` Peter Zijlstra
2018-04-05 16:21 ` James Y Knight
2018-04-04 19:32 ` Josh Poimboeuf
2018-06-07 19:23 ` Nick Desaulniers
2018-06-07 20:11 ` Greg KH
2018-04-04 9:30 ` Peter Zijlstra
2018-04-04 19:17 ` Matthias Kaehlcke
2018-04-04 20:33 ` Arnd Bergmann
2018-04-04 20:58 ` Matthias Kaehlcke
2018-04-04 21:11 ` Arnd Bergmann
2018-04-04 21:46 ` Matthias Kaehlcke
2018-04-04 21:59 ` Linus Torvalds
2018-04-04 22:17 ` Matthias Kaehlcke
2018-04-04 22:39 ` Linus Torvalds
2018-04-04 23:31 ` Matthias Kaehlcke
2018-04-05 0:05 ` Linus Torvalds
2018-04-05 0:20 ` Kees Cook
2018-04-05 7:24 ` Peter Zijlstra
2018-04-05 8:04 ` Ingo Molnar
2018-04-05 8:24 ` Peter Zijlstra
2018-04-05 16:43 ` Linus Torvalds
2018-04-05 7:20 ` Peter Zijlstra
2018-04-05 17:46 ` James Y Knight
2018-04-05 18:06 ` Linus Torvalds
2018-04-05 20:51 ` James Y Knight
2018-04-05 21:13 ` Linus Torvalds
2018-04-05 22:51 ` James Y Knight
2018-04-06 2:02 ` Linus Torvalds
2018-04-05 17:47 ` James Y Knight
2018-04-04 23:04 ` Nick Desaulniers
2018-04-03 17:36 ` Linus Torvalds
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=20180403120921.GC4082@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mka@chromium.org \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.