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] [day] [month] [year] [list]
Message-ID: <CANiq72=tuzfe__WJN3Apva7EFYA=PJcYDEFkRtu=VMyDdoL0ig@mail.gmail.com>
Date: Mon, 30 Sep 2024 19:27:56 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Guilherme Giácomo Simões <trintaeoitogc@...il.com>
Cc: Greg KH <gregkh@...uxfoundation.org>, rafael@...nel.org, ojeda@...nel.org, 
	alex.gaynor@...il.com, boqun.feng@...il.com, gary@...yguo.net, 
	bjorn3_gh@...tonmail.com, benno.lossin@...ton.me, aliceryhl@...gle.com, 
	mcgrof@...nel.org, russ.weight@...ux.dev, dakr@...hat.com, 
	a.hindborg@...nel.org, rust-for-linux@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/1] rust: device: rename "Device::from_raw()"

On Mon, Sep 30, 2024 at 6:40 PM Guilherme Giácomo Simões
<trintaeoitogc@...il.com> wrote:
>
> The 0/1 email is for explanation the motivations, attach a link for
> discussion or issue and too for explain how to test this.

Yeah, that is fine. What Greg is saying is that, when it is a single
patch, one can put that in the patch itself, below the `---` line. You
can add explanations there for each patch, and when a patch series
only has 1 patch, then you can use that space as the cover letter,
thus avoiding a 0/1 email.

Cheers,
Miguel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ