All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/5] tracing: More stuff for this merge window
Date: Thu, 05 Jun 2014 11:15:40 -0400	[thread overview]
Message-ID: <20140605151540.672365024@goodmis.org> (raw)

I know the merge window has opened early (strange), but I'm still
sorting out patches to get into 3.16 before I do any pushes.

I also just discovered that I'm not getting emails from Fengguang Wu's
kbuild bot tests. I haven't been since March. All this time I thought
I was good enough not to trigger those bugs, but I was naive. I'm still
working the issue with Fengguang, but from my SMTP error message, I had:

Sender address rejected: need fully-qualified address; from=<kbuild@bee>

That "kbuild@bee" seems to be causing it to be rejected. I wonder
how many others are not getting these emails.

Anyway, I'm pushing this out because they passed my tests. Now I
need to look at all the error reports that Fengguang's test reported
and fix them up (he gave me a link to where reports are).

Enjoy.

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next

Head SHA1: 64b8e48a72f45eedfdddfc62c25691d6c96ac919


Minchan Kim (1)
      tracing: Print max callstack on stacktrace bug

Petr Mladek (1)
      ftrace/x86: Call text_ip_addr() instead of the duplicated code

Steven Rostedt (Red Hat) (2)
      tracing: Remove unused variable in trace_benchmark
      tracing: Add __get_dynamic_array_len() macro for trace events

Yoshihiro YUNOMAE (1)
      tracing: Eliminate double free on failure of allocation on boot up

----
 arch/x86/kernel/ftrace.c       |   11 +----------
 include/trace/ftrace.h         |   11 ++++++++++-
 kernel/trace/trace.c           |    4 ----
 kernel/trace/trace_benchmark.c |    1 -
 kernel/trace/trace_stack.c     |   34 ++++++++++++++++++++++++++++++----
 5 files changed, 41 insertions(+), 20 deletions(-)

             reply	other threads:[~2014-06-05 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 15:15 Steven Rostedt [this message]
2014-06-05 15:15 ` [for-next][PATCH 1/5] tracing: Print max callstack on stacktrace bug Steven Rostedt
2014-06-05 15:15 ` [for-next][PATCH 2/5] ftrace/x86: Call text_ip_addr() instead of the duplicated code Steven Rostedt
2014-06-05 15:15 ` [for-next][PATCH 3/5] tracing: Eliminate double free on failure of allocation on boot up Steven Rostedt
2014-06-05 15:15 ` [for-next][PATCH 4/5] tracing: Remove unused variable in trace_benchmark Steven Rostedt
2014-06-05 15:15 ` [for-next][PATCH 5/5] tracing: Add __get_dynamic_array_len() macro for trace events Steven Rostedt

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=20140605151540.672365024@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 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.