mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Almeida <daniel.almeida@collabora.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Miguel Ojeda" <ojeda@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>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/4] rust: Add ARef support for work items
Date: Tue, 20 Jan 2026 11:41:03 -0300	[thread overview]
Message-ID: <1EBC2DFD-DA94-44E6-AD10-F892F57DFE5F@collabora.com> (raw)
In-Reply-To: <aW9a6KII98eI55HK@google.com>



> On 20 Jan 2026, at 07:37, Alice Ryhl <aliceryhl@google.com> wrote:
> 
> On Thu, Jan 15, 2026 at 09:35:56PM -0300, Daniel Almeida wrote:
>> This series adds ARef<T> support for both regular and delayed work items. 
>> 
>> - Patches 1 and 3 actually implement the support in workqueue.rs
>> - Patches 2 and 4 adds a corresponding implementation in drm::Device that
>>  dispatches the calls to the underlying T::Data.
>> 
>> This was tested on Tyr, and is actually needed in order to obtain a
>> &drm::Device when handling work items. This is then needed in order to
>> allocate GEM objects inside the work handler that processes the tiler OOM
>> (out of memory) events. The current series sets the stage so that the above
>> is possible in the future.
>> 
>> This is currently based on v6.19-rc5. I hope we can land all four commits
>> on a single tree, but otherwise let me know whether I should split the
>> workqueue.rs changes from the drm::Device ones and rebase accordingly.
> 
> Please send a new version that CCs workqueue maintainers.
> 
> Reviewed-by: Alice Ryhl <aliceryhl@google.com>

That was the usual “b4 prep —auto-to-cc”, perhaps we need to fix something
in MAINTAINERS?

— Daniel

      reply	other threads:[~2026-01-20 14:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16  0:35 Daniel Almeida
2026-01-16  0:35 ` [PATCH 1/4] rust: workqueue: add support for ARef<T> Daniel Almeida
2026-01-16  0:35 ` [PATCH 2/4] rust: drm: dispatch work items to the private data Daniel Almeida
2026-01-20 11:13   ` Danilo Krummrich
2026-01-16  0:35 ` [PATCH 3/4] rust: workqueue: add delayed work support for ARef<T> Daniel Almeida
2026-01-16  0:36 ` [PATCH 4/4] rust: drm: dispatch delayed work items to the private data Daniel Almeida
2026-01-20 11:14   ` Danilo Krummrich
2026-01-20 14:32     ` Daniel Almeida
2026-01-20 10:37 ` [PATCH 0/4] rust: Add ARef support for work items Alice Ryhl
2026-01-20 14:41   ` Daniel Almeida [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=1EBC2DFD-DA94-44E6-AD10-F892F57DFE5F@collabora.com \
    --to=daniel.almeida@collabora.com \
    --cc=a.hindborg@kernel.org \
    --cc=airlied@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=simona@ffwll.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome