From: Jonathan Corbet <corbet@lwn.net>
To: Matthew Wilcox <willy@infradead.org>,
Mr Tourist <zakiuddin321@gmail.com>
Cc: rdunlap@infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: reorganize kernel documentation overview for clarity
Date: Fri, 03 Oct 2025 08:25:59 -0600 [thread overview]
Message-ID: <878qhsrrig.fsf@trenco.lwn.net> (raw)
In-Reply-To: <aN5uu-yJZQiORUEL@casper.infradead.org>
Matthew Wilcox <willy@infradead.org> writes:
> On Thu, Oct 02, 2025 at 09:46:26AM +0530, Mr Tourist wrote:
>> Thanks for the review and comments provided Matthew and Randy,
>>
>> I have addressed the comments shared and have attached the updated patch
>> over the email.
>
> No, send the patch inline.
>
> Also generate the patch relative to what is currently in the tree,
> not relative to the last patch you sent.
...also, copying the documentation maintainer would be a good thing to
do...
Thanks,
jon
prev parent reply other threads:[~2025-10-03 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 11:20 [PATCH] docs: reorganize kernel documentation overview for clarity Mr Tourist
2025-10-01 17:26 ` Randy Dunlap
2025-10-02 1:12 ` Matthew Wilcox
2025-10-02 4:16 ` Mr Tourist
2025-10-02 12:23 ` Matthew Wilcox
2025-10-02 12:26 ` Bagas Sanjaya
2025-10-03 14:25 ` 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=878qhsrrig.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=willy@infradead.org \
--cc=zakiuddin321@gmail.com \
/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