From: Jakub Kicinski <kuba@kernel.org>
To: Carlos Llamas <cmllamas@google.com>
Cc: "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>,
"Suren Baghdasaryan" <surenb@google.com>,
"Donald Hunter" <donald.hunter@gmail.com>,
"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>,
"Tiffany Yang" <ynaffit@google.com>,
"John Stultz" <jstultz@google.com>,
"Shai Barack" <shayba@google.com>,
"Thiébaud Weksteen" <tweek@google.com>,
kernel-team@android.com,
"open list:ANDROID DRIVERS" <linux-kernel@vger.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>
Subject: Re: [PATCH v18 3/5] binder: introduce transaction reports via netlink
Date: Fri, 25 Jul 2025 10:38:58 -0700 [thread overview]
Message-ID: <20250725103858.109f1c5d@kernel.org> (raw)
In-Reply-To: <20250724185922.486207-4-cmllamas@google.com>
On Thu, 24 Jul 2025 18:58:57 +0000 Carlos Llamas wrote:
> +++ b/Documentation/netlink/specs/binder.yaml
We started running YAML specs thru yamllint since the previous posting
(the fixes for existing specs will reach Linus in the upcoming merge
window, IIRC). Could you double check this file for linter issues?
We use the default linting paramters, no extra config needed.
next prev parent reply other threads:[~2025-07-25 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250724185922.486207-1-cmllamas@google.com>
2025-07-24 18:58 ` [PATCH v18 3/5] binder: introduce transaction reports via netlink Carlos Llamas
2025-07-25 17:38 ` Jakub Kicinski [this message]
2025-07-25 18:07 ` Carlos Llamas
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=20250725103858.109f1c5d@kernel.org \
--to=kuba@kernel.org \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--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=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shayba@google.com \
--cc=surenb@google.com \
--cc=tkjos@android.com \
--cc=tweek@google.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