All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Dave Airlie <airlied@gmail.com>, Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: ftrace scripts and make V=1
Date: Wed, 5 Aug 2009 09:29:52 +0200	[thread overview]
Message-ID: <20090805072952.GC19322@elte.hu> (raw)
In-Reply-To: <21d7e9970908050023j2807ef3bi1321ac2a1fd9a743@mail.gmail.com>


* Dave Airlie <airlied@gmail.com> wrote:

> Hey,
> 
> So I spent 3-4 hrs today (I'm stupid yes) tracking down a .o 
> breakage by blaming rawhide gcc/binutils as I was using make 
> V=1and seeing only the compiler chain running,

Hm, is this that powerpc related build bug you just reported?

> However some ftrace script was sneaking in afterwards and screwing 
> up the .o without mentioning itself.
> 
> Surely V=1 should print all these shitty scripts its running?

Definitely, and it should print non-shitty scripts too,
just in case ;-)

	Ingo

  reply	other threads:[~2009-08-05  7:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05  7:23 ftrace scripts and make V=1 Dave Airlie
2009-08-05  7:29 ` Ingo Molnar [this message]
2009-08-06  2:00   ` Steven Rostedt
2009-08-06  2:00     ` Steven Rostedt
2009-08-06  3:43     ` Ingo Molnar
2009-08-06  3:43       ` Ingo Molnar
2009-08-06 15:02       ` Steven Rostedt
2009-08-06 15:02         ` Steven Rostedt
2009-08-06 12:25     ` [tip:tracing/urgent] tracing: do not use functions starting with .L in recordmcount.pl tip-bot for Steven Rostedt
2009-08-06 12:34       ` Ingo Molnar
2009-08-05  8:08 ` ftrace scripts and make V=1 Sam Ravnborg
2009-08-05  8:18   ` Ingo Molnar
2009-08-05  8:52 ` Andi Kleen

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=20090805072952.GC19322@elte.hu \
    --to=mingo@elte.hu \
    --cc=airlied@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sam@ravnborg.org \
    --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.