From: Jonathan Corbet <corbet@lwn.net>
To: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
Cc: rdunlap@infradead.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, bilbao@vt.edu,
Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
Subject: Re: [PATCH] docs: Extend and refactor index of further kernel docs
Date: Wed, 26 Jun 2024 16:53:58 -0600 [thread overview]
Message-ID: <87v81vxqm1.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240622194727.2171845-1-carlos.bilbao.osdev@gmail.com>
Carlos Bilbao <carlos.bilbao.osdev@gmail.com> writes:
> From: Carlos Bilbao <bilbao@vt.edu>
>
> Extend the Index of Further Kernel Documentation by adding entries for the
> Rust for Linux website, the Linux Foundation's YouTube channel, and notes
> on the second edition of Billimoria's kernel programming book. Also,
> perform some refactoring: format the text to 75 characters per line and
> sort per-section content in chronological order of publication.
>
> Signed-off-by: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
> ---
> Documentation/process/kernel-docs.rst | 68 +++++++++++++++++----------
> 1 file changed, 44 insertions(+), 24 deletions(-)
Sending this as a reply to previous postings badly confused b4, but I
did get it to apply this time, thanks.
jon
next prev parent reply other threads:[~2024-06-26 22:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 13:54 [PATCH] docs: Extend and refactor index of further kernel docs Carlos Bilbao
2024-05-30 19:34 ` Jonathan Corbet
2024-06-01 15:02 ` Carlos Bilbao
2024-06-01 15:03 ` Carlos Bilbao
2024-06-12 21:34 ` Jonathan Corbet
2024-06-12 22:17 ` Randy Dunlap
2024-06-12 23:07 ` Randy Dunlap
2024-06-12 23:10 ` Randy Dunlap
2024-06-22 19:43 ` Carlos Bilbao
2024-06-22 21:53 ` Randy Dunlap
2024-06-22 19:47 ` Carlos Bilbao
2024-06-24 14:53 ` Randy Dunlap
2024-06-26 22:53 ` Jonathan Corbet [this message]
2024-06-27 16:30 ` 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=87v81vxqm1.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao.osdev@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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