All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Steven Rostedt <srostedt@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-next@vger.kernel.org
Subject: Re: linux-next: ftrace tree build failure
Date: Tue, 25 Nov 2008 08:14:36 +0100	[thread overview]
Message-ID: <20081125071436.GA9660@elte.hu> (raw)
In-Reply-To: <20081125175708.d28d08cd.sfr@canb.auug.org.au>


* Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Steve,
> 
> On Tue, 25 Nov 2008 00:44:16 -0500 Steven Rostedt <srostedt@redhat.com> wrote:
> >
> > Yep, it was the wrong constraint used in the asm. Googling around, I
> > found a similar bug listed in gcc, which was not a bug.
> 
> Amazing what we trip over :-(
> 
> > Patch has been sent to fix this.
> 
> Can you put that patch in your tree as well, or will it reach 
> linux-next quickly enough anyway?

i've applied the assembly constraint fix to the x86 tree and i've 
integrated a new version of auto-x86-next which includes the fix, and 
pushed it out.

Thanks,

	Ingo

  reply	other threads:[~2008-11-25  7:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  3:21 linux-next: ftrace tree build failure Stephen Rothwell
2008-11-25  3:48 ` Steven Rostedt
2008-11-25  4:13   ` Stephen Rothwell
2008-11-25  4:31     ` Steven Rostedt
2008-11-25  5:09       ` Stephen Rothwell
2008-11-25  5:44         ` Steven Rostedt
2008-11-25  6:57           ` Stephen Rothwell
2008-11-25  7:14             ` Ingo Molnar [this message]
2008-11-25  7:26               ` Stephen Rothwell
2008-11-25  5:24     ` Steven Rostedt
  -- strict thread matches above, loose matches on Subject: below --
2009-01-07  0:53 Stephen Rothwell
2009-01-07  9:55 ` Ingo Molnar
2009-01-07 21:20   ` Stephen Rothwell
2009-01-02  9:07 Stephen Rothwell
2009-01-02  9:14 ` Ingo Molnar
2009-01-02 10:22   ` Stephen Rothwell
2009-01-02 11:16     ` Ingo Molnar
2008-11-25  3:07 Stephen Rothwell
2008-11-25  3:21 ` Steven Rostedt
2008-11-25  7:28 ` Ingo Molnar
2008-11-25  7:43   ` Stephen Rothwell
2008-11-25  8:04     ` Ingo Molnar
2008-11-25 14:57       ` John W. Linville
2008-11-25 18:46         ` Luis R. Rodriguez
2008-11-26  0:08           ` Stephen Rothwell
2008-11-26  0:14             ` Luis R. Rodriguez
2008-08-25  3:08 Stephen Rothwell
2008-08-25  6:05 ` Ingo Molnar
2008-08-25  6:11   ` Ingo Molnar
2008-08-25  6:31     ` Stephen Rothwell
2008-08-25  3:01 Stephen Rothwell
2008-08-25  6:09 ` Ingo Molnar
2008-08-25 16:42   ` Steven Rostedt
2008-08-25 16:46     ` Steven Rostedt
2008-08-15  2:27 Stephen Rothwell
2008-08-15  7:56 ` Ingo Molnar
2008-08-15  8:29   ` Stephen Rothwell

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=20081125071436.GA9660@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=srostedt@redhat.com \
    --cc=tglx@linutronix.de \
    /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.