[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72nb0b7yO5EBubpD63+u6quvaOTmny880DmzVwKqbeYHRA@mail.gmail.com>
Date: Wed, 30 Oct 2024 22:07:00 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Boqun Feng <boqun.feng@...il.com>
Cc: Alice Ryhl <aliceryhl@...gle.com>, Miguel Ojeda <ojeda@...nel.org>,
Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
Waiman Long <longman@...hat.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org, Andreas Hindborg <a.hindborg@...nel.org>
Subject: Re: [PATCH v6] rust: add global lock support
On Tue, Oct 29, 2024 at 10:12 PM Boqun Feng <boqun.feng@...il.com> wrote:
>
> "usually"), I submit my PR at rc2 to rc4, and tip will carry that into
Ah, so you only submit up to -rc4, got it. I didn't know what the cutoff was.
> Got it. This particular one needs to be "// SAFETY: Called exactly
> once", right?
Yeah, with an ending period (pedantic nit, but it is the style we try
to follow).
> For this I'm following the precedents in tip tree: always put the patch
> links at the last line. See the "Commit notifications" in
> Documentation/process/maintainer-tip.rst. (And yeah, I have to manually
> modify this after b4 applies the patches if you have to ask ;-))
That explains it -- thanks! Sounds good (though perhaps the bot should
be amended to agree with `b4`... :)
Cheers,
Miguel
Powered by blists - more mailing lists