linux-kernel - [PATCH 0/7] git pull request for tip/tracing/ftace

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]

Date:	Tue, 10 Feb 2009 12:35:05 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: [PATCH 0/7] git pull request for tip/tracing/ftace

Ingo,

The following is based off of tip/tracing/ftrace.

-- Steve


The following patches are in:

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

    branch: tip/tracing/ftrace


Lai Jiangshan (2):
      ring_buffer: fix typing mistake
      ring_buffer: fix ring_buffer_read_page()

Steven Rostedt (1):
      tracing, x86: fix constraint for parent variable

Tobias Klauser (1):
      tracing: storage class should be before const qualifier

Wenji Huang (3):
      tracing: remove unneeded variable
      tracing: provide correct return value after outputting the event
      tracing: fix typos in comments

----
 arch/x86/kernel/ftrace.c             |    9 +++---
 include/linux/ring_buffer.h          |    2 +-
 kernel/trace/ring_buffer.c           |   46 +++++++++++++++++++--------------
 kernel/trace/trace.c                 |    2 +-
 kernel/trace/trace_branch.c          |    4 +--
 kernel/trace/trace_functions_graph.c |   14 +++++-----
 kernel/trace/trace_hw_branches.c     |    2 +-
 kernel/trace/trace_sysprof.c         |    2 +-
 8 files changed, 42 insertions(+), 39 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/