From: Carlos Llamas <cmllamas@google.com>
To: "Alice Ryhl" <aliceryhl@google.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Christian Brauner" <brauner@kernel.org>,
"Carlos Llamas" <cmllamas@google.com>,
"Suren Baghdasaryan" <surenb@google.com>,
"Donald Hunter" <donald.hunter@gmail.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>, "Li Li" <dualli@google.com>
Cc: Tiffany Yang <ynaffit@google.com>,
John Stultz <jstultz@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
Thorsten Leemhuis <linux@leemhuis.info>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>
Subject: [PATCH] netlink: specs: binder: replace underscores with dashes in names
Date: Thu, 21 Aug 2025 13:55:21 +0000 [thread overview]
Message-ID: <20250821135522.2878772-1-cmllamas@google.com> (raw)
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>
---
Documentation/netlink/specs/binder.yaml | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/Documentation/netlink/specs/binder.yaml b/Documentation/netlink/specs/binder.yaml
index 140b77a6afee..0f0575ad1265 100644
--- a/Documentation/netlink/specs/binder.yaml
+++ b/Documentation/netlink/specs/binder.yaml
@@ -26,27 +26,27 @@ attribute-sets:
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.
-
@@ -58,7 +58,7 @@ attribute-sets:
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.
@@ -78,14 +78,14 @@ operations:
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:
--
2.51.0.rc1.193.gad69d77794-goog
next reply other threads:[~2025-08-21 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 13:55 Carlos Llamas [this message]
2025-08-21 14:37 ` Jakub Kicinski
2025-08-21 14:49 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250821135522.2878772-1-cmllamas@google.com \
--to=cmllamas@google.com \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dualli@google.com \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=joelagnelf@nvidia.com \
--cc=jstultz@google.com \
--cc=kernel-team@android.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=maco@android.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=surenb@google.com \
--cc=tkjos@android.com \
--cc=ynaffit@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®