From: Gary Guo <gary@garyguo.net>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: FUJITA Tomonori <fujita.tomonori@gmail.com>,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] rust: fix relative links to kernel header files
Date: Thu, 26 Oct 2023 15:45:25 +0100 [thread overview]
Message-ID: <20231026154525.6d14b495@eugeo> (raw)
In-Reply-To: <CANiq72=dAYc=EQnJOuBvV5cKLo85O=A1AP03F9B6nJdDwdAT1w@mail.gmail.com>
On Thu, 26 Oct 2023 13:16:05 +0200
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
> On Thu, Oct 26, 2023 at 4:09 AM FUJITA Tomonori
> <fujita.tomonori@gmail.com> wrote:
> >
> > Relative links to kernel header files are broken due to the move of
> > the output path? Looks like some of links has been broken before that.
>
> Yeah, we wanted to clean these up when these paths stabilized --
> thanks for this!
Would it be possible to use source-relative paths and then have them
fixed-up later when generating the docs? It's quite ugly and not very
maintainable to count the number of dotdots.
Best,
Gary
next prev parent reply other threads:[~2023-10-26 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 2:09 [PATCH] rust: fix relative links to kernel header files FUJITA Tomonori
2023-10-26 11:16 ` Miguel Ojeda
2023-10-26 11:40 ` [PATCH v2] " FUJITA Tomonori
2023-10-27 7:16 ` Greg KH
2023-10-26 14:45 ` Gary Guo [this message]
2023-12-15 23:59 ` [PATCH] " Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231026154525.6d14b495@eugeo \
--to=gary@garyguo.net \
--cc=fujita.tomonori@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox