[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALiyAokoDKLdZD5j-zjfheyQEz6Zy1bGyGhRFp-NmoKRGYUMmw@mail.gmail.com>
Date: Mon, 30 Sep 2024 18:00:14 +0530
From: Hridesh MG <hridesh699@...il.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Patrick Miller <paddymills@...ton.me>, 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 4:14 PM Miguel Ojeda
<miguel.ojeda.sandonis@...il.com> wrote:
> The maintainers will usually figure it out (resolving the conflicts
> when they apply them, applying them in the right order, etc.).
> Otherwise, they can also ask for one of them to be resubmitted on top
> of the other when it is too involved / subtle / large series.
>
> If you are aware that you need a patch to be put on top of another,
> then you can rebase it yourself of course. Just please make it clear
> in the cover letter (or after the `---` part) what the patches apply
> against.
>
> Cheers,
> Miguel
That makes sense. Thank you for the clarification, Miguel.
Powered by blists - more mailing lists