From: Dirk Behme <dirk.behme@de.bosch.com>
To: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>, <corbet@lwn.net>,
<ojeda@kernel.org>
Cc: <alex.gaynor@gmail.com>, <boqun.feng@gmail.com>,
<gary@garyguo.net>, <benno.lossin@proton.me>,
<a.hindborg@samsung.com>, <aliceryhl@google.com>,
<workflows@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <rust-for-linux@vger.kernel.org>,
<bilbao@vt.edu>
Subject: Re: [PATCH] kernel-docs: Add new section for Rust learning materials
Date: Thu, 12 Sep 2024 07:01:37 +0200 [thread overview]
Message-ID: <a47252d8-2833-49e3-9e8c-588a4979cbd3@de.bosch.com> (raw)
In-Reply-To: <20240911185931.16971-1-carlos.bilbao.osdev@gmail.com>
On 11.09.2024 20:59, Carlos Bilbao wrote:
> Include a new section in the Index of Further Kernel Documentation with
> resources to learn Rust. Reference it in the Rust index.
Many thanks for creating the patch! Looks nice :)
Whats about adding
https://google.github.io/comprehensive-rust/
https://docs.rust-embedded.org/book/
additionally?
Best regards
Dirk
> Signed-off-by: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
> ---
> Documentation/process/kernel-docs.rst | 111 +++++++++++++++++++++++---
> Documentation/rust/index.rst | 3 +
> 2 files changed, 103 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/process/kernel-docs.rst b/Documentation/process/kernel-docs.rst
> index 55552ec4b043..d917accd7fc3 100644
> --- a/Documentation/process/kernel-docs.rst
> +++ b/Documentation/process/kernel-docs.rst
> @@ -72,17 +72,6 @@ On-line docs
> programming. Lots of examples. Currently the new version is being
> actively maintained at https://github.com/sysprog21/lkmpg.
>
> - * Title: **Rust for Linux**
> -
> - :Author: various
> - :URL: https://rust-for-linux.com/
> - :Date: rolling version
> - :Keywords: glossary, terms, linux-kernel.
> - :Description: From the website: "Rust for Linux is the project adding
> - support for the Rust language to the Linux kernel. This website is
> - intended as a hub of links, documentation and resources related to
> - the project".
> -
> Published books
> ---------------
>
> @@ -220,6 +209,106 @@ Miscellaneous
> other original research and content related to Linux and software
> development.
>
> +Rust
> +----
> +
> + * Title: **Rust for Linux**
> +
> + :Author: various
> + :URL: https://rust-for-linux.com/
> + :Date: rolling version
> + :Keywords: glossary, terms, linux-kernel, rust.
> + :Description: From the website: "Rust for Linux is the project adding
> + support for the Rust language to the Linux kernel. This website is
> + intended as a hub of links, documentation and resources related to
> + the project".
> +
> + * Title: **Learning Rust the Dangerous Way**
> +
> + :Author: Cliff L. Biffle
> + :URL: https://cliffle.com/p/dangerust/
> + :Date: Accessed Sep 11 2024
> + :Keywords: rust, blog.
> + :Description: From the website: "LRtDW is a series of articles
> + putting Rust features in context for low-level C programmers who
> + maybe don’t have a formal CS background — the sort of people who
> + work on firmware, game engines, OS kernels, and the like.
> + Basically, people like me.". It illustrates line-by-line
> + conversions from C to Rust.
> +
> + * Title: **The Rust Book**
> +
> + :Author: Steve Klabnik and Carol Nichols, with contributions from the
> + Rust community
> + :URL: https://doc.rust-lang.org/book/
> + :Date: Accessed Sep 11 2024
> + :Keywords: rust, book.
> + :Description: From the website: "This book fully embraces the
> + potential of Rust to empower its users. It’s a friendly and
> + approachable text intended to help you level up not just your
> + knowledge of Rust, but also your reach and confidence as a
> + programmer in general. So dive in, get ready to learn—and welcome
> + to the Rust community!".
> +
> + * Title: **Rust for the Polyglot Programmer**
> +
> + :Author: Ian Jackson
> + :URL: https://www.chiark.greenend.org.uk/~ianmdlvl/rust-polyglot/index.html
> + :Date: December 2022
> + :Keywords: rust, blog, tooling.
> + :Description: From the website: "There are many guides and
> + introductions to Rust. This one is something different: it is
> + intended for the experienced programmer who already knows many
> + other programming languages. I try to be comprehensive enough to be
> + a starting point for any area of Rust, but to avoid going into too
> + much detail except where things are not as you might expect. Also
> + this guide is not entirely free of opinion, including
> + recommendations of libraries (crates), tooling, etc.".
> +
> + * Title: **Fasterthanli.me**
> +
> + :Author: Amos Wenger
> + :URL: https://fasterthanli.me/
> + :Date: Accessed Sep 11 2024
> + :Keywords: rust, blog, news.
> + :Description: From the website: "I make articles and videos about how
> + computers work. My content is long-form, didactic and exploratory
> + — and often an excuse to teach Rust!".
> +
> + * Title: **You Can't Spell Trust Without Rust**
> +
> + :Author: Alexis Beingessner
> + :URL: https://repository.library.carleton.ca/downloads/1j92g820w?locale=en
> + :Date: 2015
> + :Keywords: rust, master, thesis.
> + :Description: This thesis focuses on Rust's ownership system, which
> + ensures memory safety by controlling data manipulation and
> + lifetime, while also highlighting its limitations and comparing it
> + to similar systems in Cyclone and C++.
> +
> + * Name: **Linux Plumbers (LPC) Rust presentations**
> +
> + :Title: Rust microconference
> + :URL: https://lpc.events/event/18/sessions/186/#20240918
> + :Title: Rust for Linux
> + :URL: https://lpc.events/event/18/contributions/1912/
> + :Title: Journey of a C kernel engineer starting a Rust driver project
> + :URL: https://lpc.events/event/18/contributions/1911/
> + :Title: Crafting a Linux kernel scheduler that runs in user-space
> + using Rust
> + :URL: https://lpc.events/event/18/contributions/1723/
> + :Title: openHCL: A Linux and Rust based paravisor
> + :URL: https://lpc.events/event/18/contributions/1956/
> + :Keywords: rust, lpc, presentations.
> + :Description: A number of LPC talks related to Rust.
> +
> + * Name: **The Rustacean Station Podcast**
> +
> + :URL: https://rustacean-station.org/
> + :Keywords: rust, podcasts.
> + :Description: A community project for creating podcast content for
> + the Rust programming language.
> +
> -------
>
> This document was originally based on:
> diff --git a/Documentation/rust/index.rst b/Documentation/rust/index.rst
> index 46d35bd395cf..01f09216c229 100644
> --- a/Documentation/rust/index.rst
> +++ b/Documentation/rust/index.rst
> @@ -42,6 +42,9 @@ configurations.
> arch-support
> testing
>
> +You can also find learning materials for Rust in its section in
> +:doc:`../process/kernel-docs`.
> +
> .. only:: subproject and html
>
> Indices
--
======================================================================
Dirk Behme Robert Bosch Car Multimedia GmbH
CM/ESO2
Phone: +49 5121 49-3274 Dirk Behme
Fax: +49 711 811 5053274 PO Box 77 77 77
mailto:dirk.behme@de.bosch.com D-31132 Hildesheim - Germany
Bosch Group, Car Multimedia (CM)
Engineering SW Operating Systems 2 (ESO2)
Robert Bosch Car Multimedia GmbH - Ein Unternehmen der Bosch Gruppe
Sitz: Hildesheim
Registergericht: Amtsgericht Hildesheim HRB 201334
Aufsichtsratsvorsitzender: Dr. Dirk Hoheisel
Geschäftsführung: Dr. Steffen Berns;
Dr. Sven Ost, Jörg Pollak, Dr. Walter Schirm
======================================================================
next prev parent reply other threads:[~2024-09-12 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 18:59 Carlos Bilbao
2024-09-12 5:01 ` Dirk Behme [this message]
2024-09-13 15:33 ` Carlos Bilbao
2024-09-16 8:39 ` Miguel Ojeda
2024-09-22 15:39 ` Carlos Bilbao
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=a47252d8-2833-49e3-9e8c-588a4979cbd3@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bilbao@vt.edu \
--cc=boqun.feng@gmail.com \
--cc=carlos.bilbao.osdev@gmail.com \
--cc=corbet@lwn.net \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=workflows@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