[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72k41VmCHLFk9TAmW3VrJ=hv=e_vaVV4fjusgErVr_UmOQ@mail.gmail.com>
Date: Wed, 13 Dec 2023 19:44:43 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Benno Lossin <benno.lossin@...ton.me>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Andreas Hindborg <a.hindborg@...sung.com>,
Alice Ryhl <aliceryhl@...gle.com>,
Martin Rodriguez Reboredo <yakoyoku@...il.com>,
Asahi Lina <lina@...hilina.net>,
Sven Van Asbroeck <thesven73@...il.com>,
Viktor Garske <viktor@...ar.de>, Finn Behrens <me@...enk.dev>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] rust: macros: improve `#[vtable]` documentation
On Thu, Oct 26, 2023 at 10:20 PM Benno Lossin <benno.lossin@...ton.me> wrote:
>
> Traits marked with `#[vtable]` need to provide default implementations
> for optional functions. The C side represents these with `NULL` in the
> vtable, so the default functions are never actually called. We do not
> want to replicate the default behavior from C in Rust, because that is
> not maintainable. Therefore we should use `build_error` in those default
> implementations. The error message for that is provided at
> `kernel::error::VTABLE_DEFAULT_ERROR`.
>
> Signed-off-by: Benno Lossin <benno.lossin@...ton.me>
Applied to `rust-next` (with the requested wrapping applied and
capitalized sentence).
Thanks everyone!
Cheers,
Miguel
Powered by blists - more mailing lists