linux-kernel - Re: [RFC][PATCH 00/19] tracing: Remove "ftrace" from TRACE

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-prev] [day] [month] [year] [list]

Date:	Fri, 22 May 2015 08:46:19 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Daniel Wagner <wagi@...om.org>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Namhyung Kim <namhyung@...nel.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Jiri Olsa <jolsa@...nel.org>
Subject: Re: [RFC][PATCH 00/19] tracing: Remove "ftrace" from TRACE_EVENT
 files

On Fri, 22 May 2015 14:28:57 +0200
Daniel Wagner <wagi@...om.org> wrote:
 
> I compiled each patch individually and did some smoke testing. No
> problems found so far. I don't know if that already classifies for the
> Tested-by tag, though feel free adding it.

Thanks, but it has already been added to linux-next, which means no
more rebasing for adding tags :-/

One of my tests (done with ktest) that I do before adding anything
to linux-next is to test each patch individually to make sure it doesn't
add any new warnings or errors, and boots, and also runs a smoke test.

-- Steve

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