The usage of underscores is no longer allowed for the 'name' format in
the yaml spec. Instead, dashes should be used. This fixes the build
issue reported by Thorsten that showed up on linux-next.
Note this change has no impact on C code.
Cc: Jakub Kicinski <kuba@kernel.org>
Reported-by: Thorsten Leemhuis <linux@leemhuis.info>
Closes: https://lore.kernel.org/all/e21744a4-0155-40ec-b8c1-d81b14107c9f@leemhuis.info/
Fixes: 63740349eba7 ("binder: introduce transaction reports via netlink")
Signed-off-by: Carlos Llamas <cmllamas@google.com>
Reviewed-by: Jakub Kicinski <kuba@kernel.org>
Link: https://lore.kernel.org/r/20250821135522.2878772-1-cmllamas@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
type: string
doc: The binder context where the transaction occurred.
-
- name: from_pid
+ name: from-pid
type: u32
doc: The PID of the sender process.
-
- name: from_tid
+ name: from-tid
type: u32
doc: The TID of the sender thread.
-
- name: to_pid
+ name: to-pid
type: u32
doc: |
The PID of the recipient process. This attribute may not be present
if the target could not be determined.
-
- name: to_tid
+ name: to-tid
type: u32
doc: |
The TID of the recipient thread. This attribute may not be present
if the target could not be determined.
-
- name: is_reply
+ name: is-reply
type: flag
doc: When present, indicates the failed transaction is a reply.
-
type: u32
doc: The application-defined code from the transaction.
-
- name: data_size
+ name: data-size
type: u32
doc: The transaction payload size in bytes.
attributes:
- error
- context
- - from_pid
- - from_tid
- - to_pid
- - to_tid
- - is_reply
+ - from-pid
+ - from-tid
+ - to-pid
+ - to-tid
+ - is-reply
- flags
- code
- - data_size
+ - data-size
mcast-groups:
list: