[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240118083042.21307-1-kernel@valentinobst.de>
Date: Thu, 18 Jan 2024 09:30:42 +0100
From: Valentin Obst <kernel@...entinobst.de>
To: Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Trevor Gross <tmgross@...ch.edu>
Cc: Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...sung.com>,
Alice Ryhl <aliceryhl@...gle.com>,
rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org,
Valentin Obst <kernel@...entinobst.de>
Subject: Re: [PATCH 04/13] rust: kernel: add srctree-relative doclinks
> Hm, I wonder if we could figure out a way to make links point to
> specific definitions in the C headers with # anchors. I'm not sure
> what the intended platform to view these links is.
Currently the links simply open the plain .h file from your local tree in your
browser, i.e.,
```rust
/// [`struct wait_queue_head`]: srctree/include/linux/wait.h
```
becomes something like:
file:///mnt/build/rust-for-linux/rust4lx/include/linux/wait.h
and fragments won't work on that.
I agree that it would be nice to link to type definitions, variables,
functions, ect. in the file, maybe with something like:
```
#(type|var|func);<identifier>
```
However, I think this will require some parsing and embedding the C
source file into some html.
Powered by blists - more mailing lists