[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20251205184023.7230-1-shankari.ak0208@gmail.com>
Date: Sat, 6 Dec 2025 00:10:23 +0530
From: Shankari Anand <shankari.ak0208@...il.com>
To: Igor Korotin <igor.korotin.linux@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arve Hjønnevåg <arve@...roid.com>,
Todd Kjos <tkjos@...roid.com>,
Martijn Coenen <maco@...roid.com>,
Joel Fernandes <joelagnelf@...dia.com>,
Christian Brauner <brauner@...nel.org>,
Carlos Llamas <cmllamas@...gle.com>,
Suren Baghdasaryan <surenb@...gle.com>,
Danilo Krummrich <dakr@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>,
Alexandre Courbot <acourbot@...dia.com>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Michal Wilczynski <m.wilczynski@...sung.com>,
Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>,
Andreas Hindborg <a.hindborg@...nel.org>,
Trevor Gross <tmgross@...ch.edu>,
Daniel Almeida <daniel.almeida@...labora.com>,
Abdiel Janulgue <abdiel.janulgue@...il.com>,
Robin Murphy <robin.murphy@....com>,
Shankari Anand <shankari.ak0208@...il.com>,
linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org,
nouveau@...ts.freedesktop.org,
rust-for-linux@...r.kernel.org,
linux-pwm@...r.kernel.org
Subject: Re: [PATCH 05/10] rust: kernel: Update ARef and AlwaysRefCounted imports to use sync::aref
Hello Igor,
>
> NIT: This module already imports `AlwaysRefCounted`, so please use the
> imported name instead of the full path for consistency.
>
> > fn inc_ref(&self) {
> > // SAFETY: The existence of a shared reference guarantees that the refcount is non-zero.
> > unsafe { bindings::i2c_get_adapter(self.index()) };
>
> Thanks
> Igor
I apologize for the overlook. I was just focussing on changing the path.
I'll make the required changes and send a v2.
As this patch is part of a series, am I supposed to send all the patches with a v2,
some have been acked by already, hence I had the question?
Thanks and regards,
Shankari
Powered by blists - more mailing lists