[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023040509-tamer-clinic-c14c@gregkh>
Date: Wed, 5 Apr 2023 20:04:22 +0200
From: Greg KH <gregkh@...uxfoundation.org>
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>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
Waiman Long <longman@...hat.com>
Subject: Re: [PATCH v2 03/13] rust: lock: introduce `Mutex`
On Wed, Apr 05, 2023 at 08:03:11PM +0200, Greg KH wrote:
> On Wed, Apr 05, 2023 at 02:51:01PM -0300, Wedson Almeida Filho wrote:
> > +void rust_helper_mutex_lock(struct mutex *lock)
> > +{
> > + mutex_lock(lock);
> > +}
> > +EXPORT_SYMBOL_GPL(rust_helper_mutex_lock);
> > +
>
> No need to ever unlock a mutex?
Oh nevermind, mutex_lock() is a macro, mutex_unlock() is not...
Powered by blists - more mailing lists