The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@kernel.org>,
	gnomes@lxorguk.ukuu.org.uk, Rik van Riel <riel@redhat.com>,
	Andi Kleen <ak@linux.intel.com>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	thomas.lendacky@amd.com, Peter Zijlstra <peterz@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jiri Kosina <jikos@kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Dave Hansen <dave.hansen@intel.com>,
	Kees Cook <keescook@google.com>,
	Tim Chen <tim.c.chen@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linux-foundation.org>,
	Paul Turner <pjt@google.com>
Subject: Re: [PATCH v2] x86/retpoline: Add clang support
Date: Wed, 14 Feb 2018 08:09:06 -0800	[thread overview]
Message-ID: <20180214160906.GB6223@roeck-us.net> (raw)
In-Reply-To: <1518613769.12890.125.camel@infradead.org>

On Wed, Feb 14, 2018 at 01:09:29PM +0000, David Woodhouse wrote:
> 
> 
> On Tue, 2018-02-13 at 18:18 -0800, Guenter Roeck wrote:
> > 
> > > We're going to need the percpu.h fix too, and I'd also like to see the
> > > status of the i915 build failure you mentioned. Is there a bug filed
> > > for that already, and is it on the blocker list for 6.0? If not, why
> > > not?
> > > 
> > For my part I completely forgot about it :-(. Did you expect me to file a bug ?
> > If so, I'll need to retest and try to figure out how to do that. Let me know;
> > I should be able to get that done tomorrow.
> 
> I *thought* you had mentioned that it didn't build; in that case
> absolutely, I expected there to be a bug filed already. As a general
> rule, nobody should *ever* mention that something is broken, without
> first ensuring the bug is filed.
> 
> Looking back, I can't now see where you said that; maybe I made it up
> and I only observed this failure myself. Either way, I already filed

I found it in my e-mail logs, so it definitely was me. Or maybe both
of us in parallel.

> https://bugs.llvm.org/show_bug.cgi?id=36378 after searching bugzilla
> and not finding it.
> 
Thanks!
Guenter

      reply	other threads:[~2018-02-14 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 21:52 [PATCH v2] x86/retpoline: Add clang support Guenter Roeck
2018-02-07 22:28 ` David Woodhouse
2018-02-07 23:28   ` Guenter Roeck
2018-02-07 23:32   ` Guenter Roeck
2018-02-13 23:41     ` Guenter Roeck
2018-02-14  0:10       ` David Woodhouse
2018-02-14  2:18         ` Guenter Roeck
2018-02-14 13:09           ` David Woodhouse
2018-02-14 16:09             ` Guenter Roeck [this message]

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=20180214160906.GB6223@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=ak@linux.intel.com \
    --cc=dave.hansen@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linux-foundation.org \
    --cc=jikos@kernel.org \
    --cc=jpoimboe@redhat.com \
    --cc=keescook@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=riel@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=tim.c.chen@linux.intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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