linux-kernel - [for-next][PATCH 0/5] tracing: Some last minute updates for 3.20

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20150210170221.012858236@goodmis.org>
Date:	Tue, 10 Feb 2015 12:02:21 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [for-next][PATCH 0/5] tracing: Some last minute updates for 3.20

Some last minute updates for this merge window. Mostly documentantion
and sample code changes. Nothing risky. But they went through my entire
test suite anyway.

There is also an urgent patch that got lost in my inbox that I added.

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

Head SHA1: 7215853e985a4bef1a6c14e00e89dfec84f1e457


Steven Rostedt (Red Hat) (4):
      tracing: Update the TRACE_EVENT fields available in the sample code
      tracing: Add TRACE_EVENT_CONDITION sample
      tracing: Add TRACE_EVENT_FN example
      tracing: Add samples of DECLARE_EVENT_CLASS() and DEFINE_EVENT()

Vikram Mulukutla (1):
      tracing: Fix unmapping loop in tracing_mark_write

----
 kernel/trace/trace.c                       |   2 +-
 samples/trace_events/trace-events-sample.c |  80 ++++++-
 samples/trace_events/trace-events-sample.h | 328 +++++++++++++++++++++++++++--
 3 files changed, 395 insertions(+), 15 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/