From: "Danilo Krummrich" <dakr@kernel.org>
To: "Shankari Anand" <shankari.ak0208@gmail.com>
Cc: "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>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
"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>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>
Subject: Re: "Re: [PATCH 2/7] rust: gpu: update ARef and AlwaysRefCounted imports from sync::aref"
Date: Wed, 13 Aug 2025 18:31:38 +0200 [thread overview]
Message-ID: <DC1FZCZFDPV6.2TODOFP4YKJQR@kernel.org> (raw)
In-Reply-To: <20250813142814.31576-1-shankari.ak0208@gmail.com>
On Wed Aug 13, 2025 at 4:28 PM CEST, Shankari Anand wrote:
> This particular patch in the series is restricted to inclusion of only gpu driver files.
> Can this be picked up separately or should I be merging it with any other driver?
This specific one is fine, I'll pick it up soon.
next prev parent reply other threads:[~2025-08-13 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 9:09 [PATCH 2/7] rust: gpu: update ARef and AlwaysRefCounted imports from sync::aref Shankari Anand
2025-07-31 13:37 ` Shankari Anand
2025-07-31 13:52 ` Danilo Krummrich
2025-07-31 13:59 ` Shankari Anand
2025-07-31 14:54 ` Danilo Krummrich
2025-07-31 17:50 ` Shankari Anand
2025-08-01 8:36 ` Danilo Krummrich
2025-08-13 14:28 ` "Re: [PATCH 2/7] rust: gpu: update ARef and AlwaysRefCounted imports from sync::aref" Shankari Anand
2025-08-13 16:31 ` Danilo Krummrich [this message]
2025-08-13 16:38 ` [PATCH 2/7] rust: gpu: update ARef and AlwaysRefCounted imports from sync::aref Danilo Krummrich
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=DC1FZCZFDPV6.2TODOFP4YKJQR@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=shankari.ak0208@gmail.com \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
--cc=tzimmermann@suse.de \
/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.