[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72n5Cb9dyzRozt9_SWknm9JOuZrY0jo7sLrC9AGkdKR9Qw@mail.gmail.com>
Date: Mon, 20 May 2024 20:24:56 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Danilo Krummrich <dakr@...hat.com>, rafael@...nel.org, bhelgaas@...gle.com,
ojeda@...nel.org, alex.gaynor@...il.com, wedsonaf@...il.com,
boqun.feng@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com,
benno.lossin@...ton.me, a.hindborg@...sung.com, aliceryhl@...gle.com,
airlied@...il.com, fujita.tomonori@...il.com, lina@...hilina.net,
pstanner@...hat.com, ajanulgu@...hat.com, lyude@...hat.com,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pci@...r.kernel.org
Subject: Re: [RFC PATCH 01/11] rust: add abstraction for struct device
On Mon, May 20, 2024 at 8:00 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> What's the status of moving .rs files next to their respective .c files
> in the build system? Keeping them separate like this just isn't going
> to work, sorry.
In progress.
> > +//! Generic devices that are part of the kernel's driver model.
> > +//!
> > +//! C header: [`include/linux/device.h`](../../../../include/linux/device.h)
>
> relative paths for a common "include <linux/device.h" type of thing?
> Rust can't handle include paths from directories?
We have the custom `srctree/` notation for that (which the patch should use).
And eventually we should have support for easy-to-use links to C
structs and so on (i.e. to the C docs) -- today I happened to be
talking to the `rustdoc` maintainers about this old idea of ours.
Cheers,
Miguel
Powered by blists - more mailing lists