linux-kernel - [PATCH 0/2] tracing/triggers: A couple minor variable name changes

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: <cover.1389036657.git.tom.zanussi@linux.intel.com>
Date:	Mon,  6 Jan 2014 13:44:18 -0600
From:	Tom Zanussi <tom.zanussi@...ux.intel.com>
To:	rostedt@...dmis.org
Cc:	masami.hiramatsu.pt@...achi.com, linux-kernel@...r.kernel.org,
	Tom Zanussi <tom.zanussi@...ux.intel.com>
Subject: [PATCH 0/2] tracing/triggers: A couple minor variable name changes

This changes __tt to tt to for the recently submitted kprobes trigger patch,
and does the same for the syscall trigger invocations, which uses the same
unnecessary naming convention pointed out by Steve Rostedt.

The kprobes patch also had trivial changes resulting from the rebase
to current tracing/for-next.

The following changes since commit e0d18fe063464cb3f1a6d1939e4fcf47d92d8386:

  tracing/probes: Fix build break on !CONFIG_KPROBE_EVENT (2014-01-03 15:27:18 -0500)

are available in the git repository at:

  git://git.yoctoproject.org/linux-yocto-contrib.git tzanussi/kprobes-event-triggers-v2
  http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib/log/?h=tzanussi/kprobes-event-triggers-v2

Tom Zanussi (2):
  tracing/kprobes: Add trace event trigger invocations
  tracing: Remove double-underscore naming in syscall trigger
    invocations

 kernel/trace/trace_kprobe.c   | 42 ++++++++++++++++++++++++++++++++++++------
 kernel/trace/trace_syscalls.c | 16 ++++++++--------
 2 files changed, 44 insertions(+), 14 deletions(-)

-- 
1.8.3.1

--
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/