workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>,
	ojeda@kernel.org, dirk.behme@de.bosch.com
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,
	Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
Subject: Re: [PATCH v3] kernel-docs: Add new section for Rust learning materials
Date: Mon, 07 Oct 2024 11:20:04 -0600	[thread overview]
Message-ID: <87set7j0e3.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240922160411.274949-1-carlos.bilbao.osdev@gmail.com>

Carlos Bilbao <carlos.bilbao.osdev@gmail.com> writes:

> Include a new section in the Index of Further Kernel Documentation with
> resources to learn Rust. Reference it in the Rust index. The resources
> are a product of a survey among assistants to the conference Kangrejos'24.
>
> Signed-off-by: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
> Reviewed-by: Dirk Behme <dirk.behme@de.bosch.com>
> ---
>
> Changes since v2:
>   - Fix wrong title and added date of LPC talks.
>   - Add more resources proposed by Miguel Ojeda.
>   - Add review tag of Dirk Behme.
>
> Changes since v1:
>   - Added two more Rust blogs proposed by Dirk Behme.
>
> ---
>  Documentation/process/kernel-docs.rst | 163 ++++++++++++++++++++++++--
>  Documentation/rust/index.rst          |   3 +
>  2 files changed, 155 insertions(+), 11 deletions(-)

Applied, thanks.

jon

      parent reply	other threads:[~2024-10-07 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-22 16:04 Carlos Bilbao
2024-10-01 20:10 ` Miguel Ojeda
2024-10-07 17:20 ` Jonathan Corbet [this message]

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=87set7j0e3.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --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=dirk.behme@de.bosch.com \
    --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