From: Jakub Kicinski <kuba@kernel.org>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Carlos Llamas" <cmllamas@google.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Andrew Lunn" <andrew@lunn.ch>,
"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>,
"Matthew Maurer" <mmaurer@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Christian Brauner" <brauner@kernel.org>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v4 2/4] ynl_gen: generate Rust files from yaml files
Date: Mon, 4 May 2026 16:58:58 -0700 [thread overview]
Message-ID: <20260504165858.4882730b@kernel.org> (raw)
In-Reply-To: <20260504-binder-netlink-v4-2-601b41cd25b2@google.com>
On Mon, 04 May 2026 09:04:55 +0000 Alice Ryhl wrote:
> tools/net/ynl/pyynl/ynl_gen_c.py | 139 ++++++++++++++++++++++++++++++++++++++-
No. Rust. In. This. File.
Just commit the artifacts. I truly hope that this is the only Netlink
family we will have in Rust.
--
pw-bot: cr
next prev parent reply other threads:[~2026-05-04 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 9:04 [PATCH v4 0/4] Rust netlink support + use in Rust Binder Alice Ryhl
2026-05-04 9:04 ` [PATCH v4 1/4] rust: netlink: add raw netlink abstraction Alice Ryhl
2026-05-04 9:04 ` [PATCH v4 2/4] ynl_gen: generate Rust files from yaml files Alice Ryhl
2026-05-04 23:58 ` Jakub Kicinski [this message]
2026-05-05 9:10 ` Alice Ryhl
2026-05-04 9:04 ` [PATCH v4 3/4] rust_binder: add generated netlink.rs file Alice Ryhl
2026-05-04 9:04 ` [PATCH v4 4/4] rust_binder: report netlink transactions Alice Ryhl
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=20260504165858.4882730b@kernel.org \
--to=kuba@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=andrew@lunn.ch \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=dakr@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mmaurer@google.com \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=pabeni@redhat.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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