[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025020130-donator-entering-54da@gregkh>
Date: Sat, 1 Feb 2025 09:32:32 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Lyude Paul <lyude@...hat.com>
Cc: rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
Danilo Krummrich <dakr@...nel.org>,
MaĆra Canal <mairacanal@...eup.net>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Zijun Hu <quic_zijuhu@...cinc.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Robin Murphy <robin.murphy@....com>,
Alexander Lobakin <aleksander.lobakin@...el.com>,
Lukas Wunner <lukas@...ner.de>, Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: [PATCH] WIP: drivers/base: Add virtual_device_create()
On Thu, Jan 30, 2025 at 04:58:50PM -0500, Lyude Paul wrote:
> (FWIW: after posting this I realized I will need to split this API up a bit
> more anyway so that we can also do init/register in separate steps, since I
> realized rust will need this so we can store a reference to the device like we
> allow for normal device probes)
Do you always need to do init/register in 2 steps in rust code? Or can
you do it all in a single call? I'd prefer a single one just to make
the interface simpler overall, but if you all can't do that, I can keep
it in two, just seems wasteful.
thanks,
greg k-h
Powered by blists - more mailing lists