From: Mathieu Desnoyers Date: Thu, 15 Nov 2007 00:59:49 +0000 (-0800) Subject: Linux Kernel Markers: document format string X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=5f9468cebfdb7b809139e7682d388f9c31297936;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git Linux Kernel Markers: document format string Describes the format string standard further: Use of field names before the type specifiers.. Signed-off-by: Mathieu Desnoyers Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds --- diff --git a/Documentation/markers.txt b/Documentation/markers.txt index 295a71bc301e..d9f50a19fa0c 100644 --- a/Documentation/markers.txt +++ b/Documentation/markers.txt @@ -35,12 +35,14 @@ In order to use the macro trace_mark, you should include linux/marker.h. And, -trace_mark(subsystem_event, "%d %s", someint, somestring); +trace_mark(subsystem_event, "myint %d mystring %s", someint, somestring); Where : - subsystem_event is an identifier unique to your event - subsystem is the name of your subsystem. - event is the name of the event to mark. -- "%d %s" is the formatted string for the serializer. +- "myint %d mystring %s" is the formatted string for the serializer. "myint" and + "mystring" are repectively the field names associated with the first and + second parameter. - someint is an integer. - somestring is a char pointer.