From: "Benno Lossin" <lossin@kernel.org>
To: "Onur" <work@onurozkan.dev>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
<linux-kernel@vger.kernel.org>, <rust-for-linux@vger.kernel.org>,
<ojeda@kernel.org>, <alex.gaynor@gmail.com>, <gary@garyguo.net>,
<a.hindborg@kernel.org>, <aliceryhl@google.com>,
<tmgross@umich.edu>, <dakr@kernel.org>, <peterz@infradead.org>,
<mingo@redhat.com>, <will@kernel.org>, <longman@redhat.com>,
<felipe_life@live.com>, <daniel@sedlak.dev>,
<bjorn3_gh@protonmail.com>, <simona@ffwll.ch>,
<airlied@gmail.com>, <dri-devel@lists.freedesktop.org>,
<lyude@redhat.com>
Subject: Re: [PATCH v5 2/3] implement ww_mutex abstraction for the Rust tree
Date: Tue, 24 Jun 2025 14:48:39 +0200 [thread overview]
Message-ID: <DAURXDWGWEDV.2GZ129VC6IFKF@kernel.org> (raw)
In-Reply-To: <20250624153102.3961f377@nimda.home>
On Tue Jun 24, 2025 at 2:31 PM CEST, Onur wrote:
> On Tue, 24 Jun 2025 10:20:48 +0200
> "Benno Lossin" <lossin@kernel.org> wrote:
>
>> On Tue Jun 24, 2025 at 7:34 AM CEST, Onur wrote:
>> > Should we handle this in the initial implementation or leave it for
>> > follow-up patches after the core abstraction of ww_mutex has landed?
>>
>> Since you're writing these abstractions specifically for usage in
>> drm, I think we should look at the intended use-cases there and then
>> decide on an API.
>>
>> So maybe Lyude or Dave can chime in :)
>>
>> If you (or someone else) have another user for this API that needs it
>> ASAP, then we can think about merging this and improve it later. But
>> if we don't have a user, then we shouldn't merge it anyways.
>
> I don't think this is urgent, but it might be better to land the basic
> structure first and improve it gradually I think? I would be happy to
> continue working for the improvements as I don't plan to leave it as
> just the initial version.
I don't think we should land the basic API when we don't have a user
in-tree or blessed by the maintainers.
> I worked on the v5 review notes, but if we are going to consider
> designing a different API, then it doesn't make much sense to send a v6
> patch before finishing the design, which requires additional people in
> the topic. That would also mean some of the ongoing review discussion
> would be wasted.
I would just wait for DRM to say something :)
---
Cheers,
Benno
next prev parent reply other threads:[~2025-06-24 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250621184454.8354-1-work@onurozkan.dev>
[not found] ` <20250621184454.8354-3-work@onurozkan.dev>
[not found] ` <DASY7BECFRCT.332X5ZHZMV2W@kernel.org>
[not found] ` <aFlQ7K_mYYbrG8Cl@Mac.home>
[not found] ` <DATYHYJVPL3L.3NLMH7PPHYU9@kernel.org>
[not found] ` <aFlpFQ4ivKw81d-y@Mac.home>
[not found] ` <DAU0ELV91E2Q.35FZOII18W44J@kernel.org>
2025-06-23 17:11 ` [PATCH v5 2/3] implement ww_mutex abstraction for the Rust tree Boqun Feng
2025-06-23 23:22 ` Benno Lossin
2025-06-24 5:34 ` Onur
2025-06-24 8:20 ` Benno Lossin
2025-06-24 12:31 ` Onur
2025-06-24 12:48 ` Benno Lossin [this message]
[not found] ` <20250707163913.5ffc046d@nimda.home>
[not found] ` <DB5XIWGZ8U36.1VB58YBJFL7OT@kernel.org>
[not found] ` <20250707210613.2fd5bb55@nimda.home>
[not found] ` <DB62ZN1LTO31.1HVWDLAWJWVM8@kernel.org>
[not found] ` <FF481535-86EF-41EB-830A-1DA2434AAEA0@collabora.com>
[not found] ` <DBRVNP4MM5KO.3IXLMXKGK4XTS@kernel.org>
2025-08-02 14:15 ` Daniel Almeida
2025-08-02 20:58 ` Benno Lossin
2025-08-05 15:18 ` Daniel Almeida
2025-08-05 9:08 ` Onur Özkan
2025-08-05 12:41 ` Daniel Almeida
2025-08-05 13:50 ` Onur Özkan
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=DAURXDWGWEDV.2GZ129VC6IFKF@kernel.org \
--to=lossin@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=dakr@kernel.org \
--cc=daniel@sedlak.dev \
--cc=dri-devel@lists.freedesktop.org \
--cc=felipe_life@live.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lyude@redhat.com \
--cc=mingo@redhat.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
--cc=will@kernel.org \
--cc=work@onurozkan.dev \
/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;
as well as URLs for NNTP newsgroup(s).