[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_RzfakS8=Qr=vThJcW-eX8izBs5Xdjo+p8=Ji7Nf=_ozv0Aw@mail.gmail.com>
Date: Mon, 30 Sep 2024 13:39:44 -0300
From: Guilherme Giácomo Simões <trintaeoitogc@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: 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()"
Greg KH <gregkh@...uxfoundation.org> wrote:
>
> Was it in the 0/1 email? I didn't see it there either.
>
> And for patches where there is only one commit, you almost never need a
> 0/1 email, just put the needed information in the single patch you send
> out.
>
> thanks,
>
> greg k-h
The 0/1 email is for explanation the motivations, attach a link for
discussion or issue and too for explain how to test this.
But if you think that is not necessary, I can send a v4 without 0/1
Powered by blists - more mailing lists