linux-kernel - Re: [PATCH V2] rust: Use consistent "# Examples" heading style in rustdoc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANiq72=m+O7p==Fte4HA7kmt0DKaKmkeAQ-J1kVtyTKDKibgcA@mail.gmail.com>
Date: Thu, 12 Jun 2025 12:22:05 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Andreas Hindborg <a.hindborg@...nel.org>, Boqun Feng <boqun.feng@...il.com>, 
	Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>, 
	Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>, Gary Guo <gary@...yguo.net>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <lossin@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>, 
	Trevor Gross <tmgross@...ch.edu>, Danilo Krummrich <dakr@...nel.org>, Breno Leitao <leitao@...ian.org>, 
	"Rafael J. Wysocki" <rafael@...nel.org>, Yury Norov <yury.norov@...il.com>, 
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Luis Chamberlain <mcgrof@...nel.org>, 
	Russ Weight <russ.weight@...ux.dev>, Nishanth Menon <nm@...com>, Bjorn Helgaas <bhelgaas@...gle.com>, 
	Krzysztof Wilczyński <kwilczynski@...nel.org>, 
	Vincent Guittot <vincent.guittot@...aro.org>, linux-block@...r.kernel.org, 
	rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org, 
	linux-clk@...r.kernel.org, linux-pm@...r.kernel.org, 
	linux-pci@...r.kernel.org, Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH V2] rust: Use consistent "# Examples" heading style in rustdoc

On Thu, Jun 12, 2025 at 3:42 AM Viresh Kumar <viresh.kumar@...aro.org> wrote:
>
> If you are okay, I can also take this via the PM tree along with my other rust
> fixes for next rc.

Do you need it there? It is trivial, so it probably does not matter,
but mistakes are still possible (like it happened in v1). Since it
touches files from a few maintainers, it would be best to put it
across the "global" Rust tree (ideally with their Acked-by), and Cc
everyone (e.g. Tejun added now).

I also have a fixes PR to send, but I was not planning to take this as
a fix since it is not marked as such.

But I don't want to delay you. If you need the changes, then I would
suggest just applying the parts that modify your files, and we clean
up the rest later.

Thanks!

Cheers,
Miguel