[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bkcf6yst.fsf@samsung.com>
Date: Tue, 31 Oct 2023 07:22:59 +0000
From: Andreas Hindborg <a.hindborg@...sung.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>,
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" <rust-for-linux@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] rust: macros: improve `#[vtable]` documentation
Benno Lossin <benno.lossin@...ton.me> writes:
> 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>
Reviewed-by: Andreas Hindborg <a.hindborg@...sung.com>
Powered by blists - more mailing lists