git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] trace2: correct trace2 field name documentation

From
Josh Steadmon <steadmon@google.com>
Date
Jul 9, 2019, 23:09 UTC
Message-ID
<3f950d9fd772897edc02e9258267759d4244c1f8.1562713651.git.steadmon@google.com>

Correct the api-trace2 documentation, which lists "signal" as an expected field for the signal event type, but which actually outputs "signo" as the field name.

Signed-off-by: Josh Steadmon <steadmon@google.com>
---
This patch has been split off from the "Add a JSON Schema for trace2
events" series. The documentation discrepancy was discovered in the
process of testing the schema validation in that series.
 Documentation/technical/api-trace2.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/technical/api-trace2.txt b/Documentation/technical/api-trace2.txt
index 23c3cc7a37..fd1e628944 100644
--- a/Documentation/technical/api-trace2.txt
+++ b/Documentation/technical/api-trace2.txt
@@ -668,7 +668,7 @@ completed.)
 	"event":"signal",
 	...
 	"t_abs":0.001227,  # elapsed time in seconds
-	"signal":13        # SIGTERM, SIGINT, etc.
+	"signo":13         # SIGTERM, SIGINT, etc.
 }
 ------------
 
-- 
2.22.0.510.g264f2c817a-goog
Message 1 of 1 in “trace2: correct trace2 field name documentation”
  1. trace2: correct trace2 field name documentationJosh Steadmon, Jul 9, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.