linux-kernel - Re: [PATCH v3 2/2 RESEND] checkpatch: warn on empty rust doc comments

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: <CALiyAo=udy-P4ki1-_CAk7bHWfAjoioYEZ_ah+i6DJZ0MmmCQg@mail.gmail.com>
Date: Mon, 30 Sep 2024 16:04:43 +0530
From: Hridesh MG <hridesh699@...il.com>
To: Patrick Miller <paddymills@...ton.me>
Cc: Trevor Gross <tmgross@...ch.edu>, linux-kernel@...r.kernel.org, 
	rust-for-linux@...r.kernel.org, Andy Whitcroft <apw@...onical.com>, 
	Joe Perches <joe@...ches.com>, Dwaipayan Ray <dwaipayanray1@...il.com>, 
	Lukas Bulwahn <lukas.bulwahn@...il.com>, Miguel Ojeda <ojeda@...nel.org>, 
	Alex Gaynor <alex.gaynor@...il.com>, Wedson Almeida Filho <wedsonaf@...il.com>, 
	Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...sung.com>, 
	Alice Ryhl <aliceryhl@...gle.com>, linux-newbie@...r.kernel.org
Subject: Re: [PATCH v3 2/2 RESEND] checkpatch: warn on empty rust doc comments

On Mon, Sep 30, 2024 at 8:11 AM Patrick Miller <paddymills@...ton.me> wrote:
> After the latest revision of my patch [1], I split the if statement so that
> there is a parent check for rust files for future rust patch checks. So,
> this would perfectly fit within that block.
>
> Do you want me to add your code and credit you in my patch?
>
>
> [1]: https://lore.kernel.org/rust-for-linux/20240914181618.837227-2-paddymills@proton.me/

Please disregard my prior email, I had failed to CC everyone. Since
the change is small I'm okay with adding it as part of your patch,
please do add the Co-developed-by tag, thanks!

However, I was curious how conflicts like these are generally
resolved. For example, if there are two large patchsets which conflict
with each other, how does one ensure that they are compatible, and
even if they are, how do the maintainers ensure that they are applied
in the correct order?