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 v2] kernel-docs: Add new section for Rust learning materials
Date: Mon, 16 Sep 2024 07:33:03 +0200 [thread overview]
Message-ID: <3a421753-07fa-451a-90fa-e04d1a731b1a@de.bosch.com> (raw)
In-Reply-To: <20240913153824.161150-1-carlos.bilbao.osdev@gmail.com>
On 13.09.2024 17:38, 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.
>
> Signed-off-by: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
Many thanks!
Two minor things below. With these:
Reviewed-by: Dirk Behme <dirk.behme@de.bosch.com>
Dirk
> ---
>
> Changes since v1:
> - Added two more Rust blogs proposed by Dirk Behme.
>
> ---
> Documentation/process/kernel-docs.rst | 131 +++++++++++++++++++++++---
> Documentation/rust/index.rst | 3 +
> 2 files changed, 123 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/process/kernel-docs.rst b/Documentation/process/kernel-docs.rst
> index 55552ec4b043..b56c2adcb954 100644
> --- a/Documentation/process/kernel-docs.rst
> +++ b/Documentation/process/kernel-docs.rst
> @@ -72,17 +72,6 @@ On-line docs
...
> + * Title: **Learning Rust the Dangerous Way**
It looks to me the that it is called "Learn" and not "Learning"?
...
> + * Name: **Linux Plumbers (LPC) Rust presentations**
Here I would add the year "2024" somewhere. There have been previous
LPCs and most probably there will be some in the next years ;)
next prev parent reply other threads:[~2024-09-16 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 15:38 Carlos Bilbao
2024-09-16 5:33 ` Dirk Behme [this message]
2024-09-22 15:22 ` 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=3a421753-07fa-451a-90fa-e04d1a731b1a@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
all inboxes | Powered by JetHome®