From: Jonathan Corbet <corbet@lwn.net>
To: Carlos Bilbao <bilbao@vt.edu>,
ojeda@kernel.org, alex.gaynor@gmail.com, wedsonaf@gmail.com,
boqun.feng@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Carlos Bilbao <bilbao@vt.edu>
Subject: Re: [RFC] Integrate Rust code documentation into Documentation/
Date: Mon, 21 Nov 2022 14:39:53 -0700 [thread overview]
Message-ID: <87o7t07zrq.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221119165921.18806-1-bilbao@vt.edu>
Carlos Bilbao <bilbao@vt.edu> writes:
> I propose we include in 'make htmldocs' the option to integrate
> rustdoc-generated information. We could create and use
> Documentation/rust/rustdoc.rst as linking point for that HTML. This
> wouldn't be costly for the kernel itself. More importantly, the kernel
> website could host this information by default.
I'm all in favor of including that output, just haven't had the time to
try to figure out how to make it actually work. Got a patch that
implements this behavior? :)
jon
next parent reply other threads:[~2022-11-21 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221119165921.18806-1-bilbao@vt.edu>
2022-11-21 21:39 ` Jonathan Corbet [this message]
2022-11-21 23:52 ` [RFC] Integrate Rust code documentation into Documentation/ 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=87o7t07zrq.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=alex.gaynor@gmail.com \
--cc=bilbao@vt.edu \
--cc=boqun.feng@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=wedsonaf@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).