Re: [RFC PATCH 1/3] trace2: correct trace2 field name documentation

2019-06-14 Thread Jeff Hostetler
On 6/11/2019 7:31 PM, Josh Steadmon wrote: 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 --- Documentation/technical/api-trace2.txt | 2 +- 1 fil

Re: [RFC PATCH 1/3] trace2: correct trace2 field name documentation

2019-06-12 Thread Josh Steadmon
On 2019.06.12 11:00, Junio C Hamano wrote: > Josh Steadmon writes: > > > 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. > > > Nice. Is this one of the findings made by your

Re: [RFC PATCH 1/3] trace2: correct trace2 field name documentation

2019-06-12 Thread Junio C Hamano
Josh Steadmon writes: > 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. Nice. Is this one of the findings made by your validation, by the way? > > Signed-off-by: Josh Steadmon

[RFC PATCH 1/3] trace2: correct trace2 field name documentation

2019-06-11 Thread Josh Steadmon
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 --- Documentation/technical/api-trace2.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --g