From: Randy Dunlap <rdunlap@infradead.org>
To: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
bilbao@vt.edu
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Extend and refactor index of further kernel docs
Date: Sat, 22 Jun 2024 14:53:36 -0700 [thread overview]
Message-ID: <e5c58296-dc05-4df2-966b-2e5b1cdf0e4e@infradead.org> (raw)
In-Reply-To: <e6bf0675-f542-482d-a861-000772b1d10e@gmail.com>
On 6/22/24 12:43 PM, Carlos Bilbao wrote:
> Hello folks,
>
> On 6/12/24 17:17, Randy Dunlap wrote:
>
>>
>> On 6/1/24 8:03 AM, Carlos Bilbao wrote:
>>> 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(-)
>>>
>>> diff --git a/Documentation/process/kernel-docs.rst
>>> b/Documentation/process/kernel-docs.rst
>> The 2 lines above should be on one line, but fixing that doesn't fix everything.
>> 'patch' still says that it's a malformed patch.
>>
>> Carlos, please check Documentation/process/email-clients.rst section on
>> Thunderbird, especially for line length and line wrap.
>>
>> I'm still looking...
>
>
> I followed the instructions for Thunderbird but atm I'm tired of trying to
> make it work. I'll just go back to using 'git send-email' for patches. I'm
> resending this patch like that.
>
Good plan. :)
>
>>
>>> index 8660493b91d0..6f3e290abd22 100644
>>> --- a/Documentation/process/kernel-docs.rst
>>> +++ b/Documentation/process/kernel-docs.rst
>>> @@ -3,27 +3,27 @@
>>> Index of Further Kernel Documentation
>>> =====================================
>
> Thanks,
> Carlos
--
~Randy
next prev parent reply other threads:[~2024-06-22 21:53 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 [this message]
2024-06-22 19:47 ` Carlos Bilbao
2024-06-24 14:53 ` Randy Dunlap
2024-06-26 22:53 ` Jonathan Corbet
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=e5c58296-dc05-4df2-966b-2e5b1cdf0e4e@infradead.org \
--to=rdunlap@infradead.org \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao.osdev@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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).