From: Michal Wilczynski <m.wilczynski@samsung.com>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: "Shankari Anand" <shankari.ak0208@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Christian Brauner" <brauner@kernel.org>,
"Carlos Llamas" <cmllamas@google.com>,
"Suren Baghdasaryan" <surenb@google.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Igor Korotin" <igor.korotin.linux@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Abdiel Janulgue" <abdiel.janulgue@gmail.com>,
"Robin Murphy" <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
nouveau@lists.freedesktop.org, rust-for-linux@vger.kernel.org,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH 06/10] rust: kernel: Update ARef and AlwaysRefCounted imports to use sync::aref
Date: Wed, 26 Nov 2025 12:34:23 +0100 [thread overview]
Message-ID: <cca5c7e8-d9c4-4e28-8da2-62dd521ceea3@samsung.com> (raw)
In-Reply-To: <CANiq72mQ4cu9wehGKxS92EK2H3kcX8XPpRmv2DdYmn6Ve9iDAw@mail.gmail.com>
On 11/25/25 13:31, Miguel Ojeda wrote:
> On Mon, Nov 24, 2025 at 5:10 PM Uwe Kleine-König
> <u.kleine-koenig@baylibre.com> wrote:
>>
>> having no clue about Rust:
>>
>> Can this patch be applied independent of the others via the pwm tree? If
>> I understand correctly it's only patch #10 that depends on the previous
>> patches, right?
>>
>> Is there already a merge plan for this series?
>
> Yeah, if subsystems pick the independent patches at their own pace,
> then that is great, so please do!
>
> Then, after 1 or 2 cycles, we can do the flag day change on the Rust
> tree (with any last changes needed Ack'd, but ideally there will be
> none remaining).
>
> It is what did in similar cases for renaming (or moving across the
> path hierarchy) things in Rust. For simple things that get Ack'd quick
> enough by everyone, sometimes we may be able to take everything in the
> Rust tree.
>
> Thanks!
>
> Cheers,
> Miguel
>
I think code wise it's fine, provided the subject is fixed like Uwe suggested.
Acked-by: Michal Wilczynski <m.wilczynski@samsung.com>
next prev parent reply other threads:[~2025-11-26 11:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 9:24 [PATCH 00/10] rust: refactor ARef and AlwaysRefCounted imports Shankari Anand
2025-11-23 9:24 ` [PATCH 01/10] drivers: android: binder: Update ARef imports from sync::aref Shankari Anand
2025-11-25 12:24 ` Alice Ryhl
2025-11-23 9:24 ` [PATCH 02/10] drivers: gpu: " Shankari Anand
2025-11-24 12:16 ` Alexandre Courbot
2025-11-24 21:20 ` Joel Fernandes
2025-11-23 9:24 ` [PATCH 03/10] rust: device: Update ARef and AlwaysRefCounted " Shankari Anand
2025-11-23 9:24 ` [PATCH 04/10] rust: drm: Update AlwaysRefCounted imports to use sync::aref Shankari Anand
2025-11-23 9:24 ` [PATCH 05/10] rust: kernel: Update ARef and " Shankari Anand
2025-11-23 13:16 ` Igor Korotin
2025-11-29 12:21 ` Igor Korotin
2025-12-05 18:40 ` Shankari Anand
2025-11-23 9:24 ` [PATCH 06/10] " Shankari Anand
2025-11-24 16:10 ` Uwe Kleine-König
2025-11-25 12:31 ` Miguel Ojeda
2025-11-26 11:34 ` Michal Wilczynski [this message]
2025-11-27 6:25 ` Uwe Kleine-König
2025-11-23 9:24 ` [PATCH 07/10] rust: kernel: Update ARef " Shankari Anand
2025-11-23 9:24 ` [PATCH 08/10] rust: kernel: Update AlwaysRefCounted " Shankari Anand
2025-11-23 9:24 ` [PATCH 09/10] samples: rust: Update ARef " Shankari Anand
2025-11-23 9:24 ` [PATCH 10/10] rust: kernel: remove temporary re-exports of ARef and AlwaysRefCounted Shankari Anand
2025-11-25 12:39 ` [PATCH 00/10] rust: refactor ARef and AlwaysRefCounted imports Alice Ryhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cca5c7e8-d9c4-4e28-8da2-62dd521ceea3@samsung.com \
--to=m.wilczynski@samsung.com \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=igor.korotin.linux@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maco@android.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=shankari.ak0208@gmail.com \
--cc=simona@ffwll.ch \
--cc=surenb@google.com \
--cc=tkjos@android.com \
--cc=tmgross@umich.edu \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@baylibre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).