From: "Danilo Krummrich" <dakr@kernel.org>
To: "Gary Guo" <gary@garyguo.net>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
"Matteo Kloiber" <kernel@matt3o12.de>,
"Robin Murphy" <robin.murphy@arm.com>, <aliceryhl@google.com>,
<ojeda@kernel.org>, <airlied@gmail.com>, <simona@ffwll.ch>,
<abdiel.janulgue@gmail.com>, <daniel.almeida@collabora.com>,
<a.hindborg@kernel.org>, <nova-gpu@lists.linux.dev>,
<dri-devel@lists.freedesktop.org>, <driver-core@lists.linux.dev>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] rust: scatterlist: honor the device's maximum segment size
Date: Mon, 28 Sep 2026 20:22:39 +0200 [thread overview]
Message-ID: <DLR5Q993RA06.3UA51L951IFX0@kernel.org> (raw)
In-Reply-To: <DLR4TIXBL0K0.3GNRPD2HU6S4T@garyguo.net>
On Mon Sep 28, 2026 at 7:39 PM CEST, Gary Guo wrote:
> I was quite skeptical whether the complication of adding the dma setup token is
> worth the effort, but the capacity struct sounds like a very nice design as it's
> infinitely extensible. I can foresee that we might want to eventually get rid of
> the special `Core` typestate and just replace everything with setup
> capabilities.
I had a similar thought (which is one of the reasons I proposed it), but I don't
think we can replace the Core type state entirely.
There's more than just one bus callback that holds the Core type state, so I
think the bus setup token is rather the (much) better version of a Probe type
state.
next prev parent reply other threads:[~2026-09-28 18:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 23:32 [PATCH 0/2] rust: honor the maximum DMA " Matteo Kloiber
2026-08-31 23:32 ` [PATCH 1/2] gpu: nova-core: declare unlimited DMA max " Matteo Kloiber
2026-09-07 2:10 ` Alexandre Courbot
2026-09-13 21:07 ` Matteo Kloiber
2026-08-31 23:32 ` [PATCH 2/2] rust: scatterlist: honor the device's maximum " Matteo Kloiber
2026-09-07 2:43 ` Alexandre Courbot
2026-09-13 21:08 ` Matteo Kloiber
2026-09-14 0:45 ` Alexandre Courbot
2026-09-14 9:58 ` Danilo Krummrich
2026-09-14 10:22 ` Gary Guo
2026-09-14 12:17 ` Robin Murphy
2026-09-14 13:17 ` Gary Guo
2026-09-14 13:57 ` Danilo Krummrich
2026-09-17 9:06 ` Alexandre Courbot
2026-09-27 22:44 ` Matteo Kloiber
2026-09-28 15:05 ` Alexandre Courbot
2026-09-28 17:39 ` Gary Guo
2026-09-28 18:22 ` Danilo Krummrich [this message]
2026-09-15 4:44 ` Alexandre Courbot
2026-09-15 4:52 ` Alexandre Courbot
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=DLR5Q993RA06.3UA51L951IFX0@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=driver-core@lists.linux.dev \
--cc=gary@garyguo.net \
--cc=kernel@matt3o12.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rust-for-linux@vger.kernel.org \
--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
all inboxes | Powered by JetHome®