From: "Danilo Krummrich" <dakr@kernel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>
Cc: "Igor Korotin" <igor.korotin.linux@gmail.com>,
wsa+renesas@sang-engineering.com,
"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>,
"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>,
"Michal Wilczynski" <m.wilczynski@samsung.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, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v2 2/4] rust: i2c: Update ARef and AlwaysRefCounted imports to use sync::aref
Date: Sun, 04 Jan 2026 13:09:15 +0100 [thread overview]
Message-ID: <DFFSKWSC1SHC.32YAJT1GI79IY@kernel.org> (raw)
In-Reply-To: <CANiq72=YKO3fvX=CP1VeXoKfROtdJWF3rysNdz+k_nOWw1jv2A@mail.gmail.com>
On Sun Jan 4, 2026 at 12:58 PM CET, Miguel Ojeda wrote:
> On Sun, Jan 4, 2026 at 12:31 AM Igor Korotin
> <igor.korotin.linux@gmail.com> wrote:
>>
>> I see this change more as a Rust infrastructure change rather than
>> something I2C-specific.
>>
>> If it is not a burden for you, I would appreciate it if you could take
>> it through your tree.
>
> This could even go through the Rust tree since it is a general
> cleanup, but I imagine Danilo wanted to see what Wolfram thinks first,
> since it is the "parent" subsystem.
Yes, that was the intention. I think it is a good thing if the C and Rust parts
of subsystems are handled closely. I think making even trivial patches flow
through the corresponding trees can help with that. :)
next prev parent reply other threads:[~2026-01-04 12:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 20:27 [PATCH v2 0/4] rust: refactor ARef and AlwaysRefCounted imports Shankari Anand
2026-01-02 20:27 ` [PATCH v2 1/4] drivers: android: binder: Update ARef imports from sync::aref Shankari Anand
2026-01-31 11:35 ` Shankari Anand
2026-02-03 11:57 ` Greg Kroah-Hartman
2026-01-02 20:27 ` [PATCH v2 2/4] rust: i2c: Update ARef and AlwaysRefCounted imports to use sync::aref Shankari Anand
2026-01-03 18:45 ` Igor Korotin
2026-01-03 20:18 ` Danilo Krummrich
2026-01-03 23:31 ` Igor Korotin
2026-01-04 11:58 ` Miguel Ojeda
2026-01-04 12:09 ` Danilo Krummrich [this message]
2026-01-04 12:14 ` Miguel Ojeda
2026-01-02 20:27 ` [PATCH v2 3/4] rust: usb: Update " Shankari Anand
2026-01-31 11:41 ` Shankari Anand
2026-01-02 20:27 ` [PATCH v2 4/4] rust: types: remove temporary re-exports of ARef and AlwaysRefCounted Shankari Anand
2026-01-03 4:28 ` kernel test robot
2026-03-07 15:26 ` [PATCH v2 0/4] rust: refactor ARef and AlwaysRefCounted imports Shankari Anand
2026-03-07 15:43 ` Miguel Ojeda
2026-03-11 16:19 ` Shankari Anand
2026-03-15 21:23 ` Miguel Ojeda
2026-03-15 21:25 ` Miguel Ojeda
2026-03-16 5:32 ` Wolfram Sang
2026-03-16 6:08 ` Greg Kroah-Hartman
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=DFFSKWSC1SHC.32YAJT1GI79IY@kernel.org \
--to=dakr@kernel.org \
--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=daniel.almeida@collabora.com \
--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=lossin@kernel.org \
--cc=m.wilczynski@samsung.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maco@android.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mripard@kernel.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=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.