[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <0A0C1EFC-29A1-4D73-8B02-CC1C693D6A7A@collabora.com>
Date: Fri, 12 Jul 2024 12:13:15 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Danilo Krummrich <dakr@...hat.com>
Cc: Steven Price <steven.price@....com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
ojeda@...nel.org,
lyude@...hat.com,
robh@...nel.org,
lina@...hilina.net,
mcanal@...lia.com,
airlied@...il.com,
rust-for-linux@...r.kernel.org,
dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] drm: panthor: add dev_coredumpv support
> On 12 Jul 2024, at 11:53, Danilo Krummrich <dakr@...hat.com> wrote:
>
> You could also just define those structures in a C header directly and use it
> from Rust, can't you?
>
Sure, I am open to any approach here. Although this looks a bit reversed to me.
i.e.: why should I declare these structs in a separate language and file, and then use them in Rust through bindgen? Sounds clunky.
Right now, they are declared right next to where they are used in the code, i.e.: in the same Rust file. And so long as they’re #[repr(C)] we know that an equivalent C version can generated by cbindgen.
Powered by blists - more mailing lists