[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72mELB=pHS2ocK8z51h1BhhySzV3PSTD98F+YTB3EbZ_uw@mail.gmail.com>
Date: Sat, 22 Apr 2023 01:47:00 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Wedson Almeida Filho <wedsonaf@...il.com>
Cc: rust-for-linux@...r.kernel.org, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
linux-kernel@...r.kernel.org,
Wedson Almeida Filho <walmeida@...rosoft.com>,
Martin Rodriguez Reboredo <yakoyoku@...il.com>
Subject: Re: [PATCH v4.1] rust: lock: add `Guard::do_unlocked`
On Wed, Apr 12, 2023 at 2:14 PM Wedson Almeida Filho <wedsonaf@...il.com> wrote:
>
> It releases the lock, executes some function provided by the caller,
> then reacquires the lock. This is preparation for the implementation of
> condvars, which will sleep after between unlocking and relocking.
Applied to `rust-next` within the main series, with the irqsave bits
removed as discussed. Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists