From: Danilo Krummrich <dakr@kernel.org>
To: Lyude Paul <lyude@redhat.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org, Gary Guo <gary@garyguo.net>,
Miguel Ojeda <ojeda@kernel.org>, Simona Vetter <simona@ffwll.ch>,
Alice Ryhl <aliceryhl@google.com>,
Nova-gpu@lists.linux.dev,
Shankari Anand <shankari.ak0208@gmail.com>,
David Airlie <airlied@gmail.com>,
Benno Lossin <lossin@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Asahi Lina <lina+kernel@asahilina.net>,
"Mukesh Kumar Chaurasiya (IBM)" <mkchauras@gmail.com>,
Daniel Almeida <daniel.almeida@collabora.com>
Subject: Re: [PATCH v6 0/3] Introduce DeviceContext
Date: Tue, 2 Jun 2026 23:07:01 +0200 [thread overview]
Message-ID: <20260602210701.1705071-1-dakr@kernel.org> (raw)
In-Reply-To: <20260507220044.3204919-1-lyude@redhat.com>
On Thu, 7 May 2026 17:59:18 -0400, Lyude Paul wrote:
> [PATCH v6 0/3] Introduce DeviceContext
Applied, thanks!
Branch: drm-rust-next
Tree: https://gitlab.freedesktop.org/drm/rust/kernel.git
[1/3] rust/drm: Introduce DeviceContext
commit: 571d4242c466
[2/3] rust/drm/gem: Add DriverAllocImpl type alias
commit: 43a5d04a743b
[3/3] rust/drm/gem: Use DeviceContext with GEM objects
commit: 0023a1e8d01a
The patches will appear in the next linux-next integration (typically within 24
hours on weekdays).
The patches are queued up for the upcoming merge window for the next major
kernel release.
prev parent reply other threads:[~2026-06-02 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 21:59 [PATCH v6 0/3] Introduce DeviceContext Lyude Paul
2026-05-07 21:59 ` [PATCH v6 1/3] rust/drm: " Lyude Paul
2026-05-07 21:59 ` [PATCH v6 2/3] rust/drm/gem: Add DriverAllocImpl type alias Lyude Paul
2026-05-07 21:59 ` [PATCH v6 3/3] rust/drm/gem: Use DeviceContext with GEM objects Lyude Paul
2026-06-02 21:07 ` Danilo Krummrich [this message]
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=20260602210701.1705071-1-dakr@kernel.org \
--to=dakr@kernel.org \
--cc=Nova-gpu@lists.linux.dev \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=lina+kernel@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=mkchauras@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=shankari.ak0208@gmail.com \
--cc=simona@ffwll.ch \
/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