From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: rust-for-linux <rust-for-linux@vger.kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: https://rust.docs.kernel.org is now available
Date: Sun, 18 Aug 2024 16:08:26 +0200 [thread overview]
Message-ID: <CANiq72nSwGou23kFU9v8=CW_78WzVbCVhfDL=SNZja8aBLCRSQ@mail.gmail.com> (raw)
Hi all,
The Rust code documentation (i.e. `rustdoc`-generated docs) is now available at:
https://rust.docs.kernel.org
For linux-next, see:
https://rust.docs.kernel.org/next/
There are also tags for each main release, e.g. for the current stable kernel:
https://rust.docs.kernel.org/6.10/
The generation uses a particular kernel configuration, based on x86_64, which
may get tweaked over time. Older tags, and how they are generated, may also
change in the future. We may consider freezing them at some point, but for the
moment, please do not consider the content to be immutable.
Thanks Konstantin for the support setting it up!
Cheers,
Miguel
reply other threads:[~2024-08-18 14:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CANiq72nSwGou23kFU9v8=CW_78WzVbCVhfDL=SNZja8aBLCRSQ@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).