linux-kernel - Re: [PATCH v3] rust: doc: Clean up formatting in io.rs

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: <CAFttn56vNVcE=pcGgxGrSZf=r=h_ceFwEf+D71yc9GnANww5Aw@mail.gmail.com>
Date: Mon, 2 Jun 2025 16:41:20 +0530
From: Sai Vishnu <saivishnu725@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Miguel Ojeda <ojeda@...nel.org>, alex.gaynor@...il.com, boqun.feng@...il.com, 
	gary@...yguo.net, bjorn3_gh@...tonmail.com, Benno Lossin <lossin@...nel.org>, 
	a.hindborg@...nel.org, aliceryhl@...gle.com, tmgross@...ch.edu, 
	dakr@...nel.org, daniel.almeida@...labora.com, me@...enk.dev
Subject: Re: [PATCH v3] rust: doc: Clean up formatting in io.rs

> below the first --- line

Is it the one below the Signed off by line? To get the complete picture:
1. commit title
2. commit message
3. signed off and other tags
---
4. The version log or any other necessary comments
5. actual diff
---

Additionally, I suppose the `base-commit` tag should also be placed in
3 (above/below Signed-off-by), as it was added to the very end by
`git` when generating the patch.
I am sincerely apologizing for taking at least 4 versions for a simple
fix, but I am trying to figure out how to properly create and send
patches.
This clearly explains what you meant:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#commentary
.
I will send v4 after thoroughly reading it multiple times.

Thanks for all the time and patience!