[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=D6P+x99Ur0jKnR+7DoE=vS0X1jnphZ5E3i-Br6tsh3Q@mail.gmail.com>
Date: Mon, 30 Oct 2023 12:22:50 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Benno Lossin <benno.lossin@...ton.me>, FUJITA Tomonori <fujita.tomonori@...il.com>,
boqun.feng@...il.com, netdev@...r.kernel.org, rust-for-linux@...r.kernel.org,
tmgross@...ch.edu, wedsonaf@...il.com
Subject: Re: [PATCH net-next v7 1/5] rust: core abstractions for network PHY drivers
On Sat, Oct 28, 2023 at 8:24 PM Andrew Lunn <andrew@...n.ch> wrote:
>
> Please could you help me understand the consequences here. Are you
> saying the rust toolchain is fatally broken here, it cannot generate
> valid code at the moment? As a result we need to wait for a new
> version of bindgen?
Benno has already replied, but to be extra clear: no, it is not
"fatally broken".
`bindgen` is just a tool to automate writing some things you would
otherwise need to manually write. It currently generates some methods
that take a reference, but we should avoid creating references in this
case, so we would like methods that take a pointer instead. That's it.
In other words, we could simply write the methods ourselves. That
would be "Option 0" (which would be like Benno's 1, but manually; or
like Benno's 2, but in Rust).
Cheers,
Miguel
Powered by blists - more mailing lists