From: "Gary Guo" <gary@garyguo.net>
To: "Alice Ryhl" <aliceryhl@google.com>,
"Danilo Krummrich" <dakr@kernel.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "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>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [drm-rust-next PATCH 0/2] Fix sync::aref imports
Date: Thu, 26 Mar 2026 15:43:05 +0000 [thread overview]
Message-ID: <DHCTUR680RWK.PFYB70EBQL2H@garyguo.net> (raw)
In-Reply-To: <20260326-drm-rust-next-fix-aref-v1-0-7f6f58d2828a@google.com>
On Thu Mar 26, 2026 at 3:25 PM GMT, Alice Ryhl wrote:
> A few imports of types::ARef were merged into drm-rust-next, but this
> old path is being removed in rust-next this cycle. Thus update them.
>
> Signed-off-by: Alice Ryhl <aliceryhl@google.com>
> ---
> Alice Ryhl (2):
> rust: workqueue: use new sync::aref path for imports
> rust: drm: use new sync::aref path for imports
>
> rust/kernel/drm/gem/mod.rs | 2 +-
> rust/kernel/workqueue.rs | 8 +++++---
> 2 files changed, 6 insertions(+), 4 deletions(-)
> ---
> base-commit: 206bada308d0d715d62ac841784af34a2ca22ff6
> change-id: 20260326-drm-rust-next-fix-aref-595e7bd5e70c
>
> Best regards,
Reviewed-by: Gary Guo <gary@garyguo.net>
(with import style fixed up)
next prev parent reply other threads:[~2026-03-26 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 15:25 [drm-rust-next PATCH 0/2] Fix sync::aref imports Alice Ryhl
2026-03-26 15:25 ` [PATCH drm-rust-next 1/2] rust: workqueue: use new sync::aref path for imports Alice Ryhl
2026-03-26 15:25 ` [PATCH drm-rust-next 2/2] rust: drm: " Alice Ryhl
2026-03-26 15:34 ` [drm-rust-next PATCH 0/2] Fix sync::aref imports Danilo Krummrich
2026-03-26 15:36 ` Alice Ryhl
2026-03-26 15:43 ` Gary Guo [this message]
2026-03-26 15:49 ` Alice Ryhl
2026-03-26 15:50 ` 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=DHCTUR680RWK.PFYB70EBQL2H@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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.