All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Fengguang Wu <wfg@linux.intel.com>
Subject: Re: [PATCH][GIT PULL][v3.5] ftrace: Make all inline tags also include notrace
Date: Mon, 18 Jun 2012 10:56:26 +0200	[thread overview]
Message-ID: <20120618085626.GA28824@gmail.com> (raw)
In-Reply-To: <1339714048.13377.246.camel@gandalf.stny.rr.com>


* Steven Rostedt <rostedt@goodmis.org> wrote:

>     ftrace: Make all inline tags also include notrace
>     
>     Commit 5963e317b1 ftrace/x86: Do not change stacks in DEBUG when calling lockdep
>     prevented lockdep calls from the int3 breakpoint handler from reseting the
>     stack if a function that was called was in the process of being converted
>     for tracing and had a breakpoint on it.

That's now how we refer to commits ...

>     Commit 45959ee7 ftrace: Do not function trace inlined functions
>     only touched the 'inline' tags when CONFIG_OPMITIZE_INLINING was enabled.

neither this :-/

We tend to write it like this:

      Commit 45959ee7aa64 ("ftrace: Do not function trace 
      inlined functions") only touched the 'inline' tags when 
      CONFIG_OPMITIZE_INLINING was enabled.

Thanks,

	Ingo

  reply	other threads:[~2012-06-18  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 22:47 [PATCH][GIT PULL][v3.5] ftrace: Make all inline tags also include notrace Steven Rostedt
2012-06-18  8:56 ` Ingo Molnar [this message]
2012-06-18 12:25   ` Steven Rostedt
2012-06-18 14:00     ` Ingo Molnar

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=20120618085626.GA28824@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=wfg@linux.intel.com \
    /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.