From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
Alok Tiwari <alok.a.tiwari@oracle.com>,
pbonzini@redhat.com, kvm@vger.kernel.org,
linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH next] Documentation: KVM: fix reference for kvm_ppc_resize_hpt and various typos
Date: Tue, 24 Jun 2025 20:45:07 +0700 [thread overview]
Message-ID: <f833718d-ea25-4e21-a103-4ee0153ca990@gmail.com> (raw)
In-Reply-To: <87jz5171lk.fsf@trenco.lwn.net>
On 6/24/25 19:42, Jonathan Corbet wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
>
>> On Mon, Jun 23, 2025 at 12:11:47PM -0700, Alok Tiwari wrote:
>>> If this ioctl is called when a hash table has already been allocated,
>>> with a different order from the existing hash table, the existing hash
>>> -table will be freed and a new one allocated. If this is ioctl is
>>> -called when a hash table has already been allocated of the same order
>>> +table will be freed and a new one allocated. If this ioctl is called
>>> +when a hash table has already been allocated of the same order
>>
>> Two spaces between sentences (just to be consistent), please.
>
> Spaces after periods are explicitly documented as something we do not
> "correct" or harass our contributors about. Please, for the Nth time,
> do not add unnecessary friction to the process of improving our
> documentation.
>
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-06-24 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 19:11 [PATCH next] Documentation: KVM: fix reference for kvm_ppc_resize_hpt and various typos Alok Tiwari
2025-06-23 23:24 ` Bagas Sanjaya
2025-06-24 12:42 ` Jonathan Corbet
2025-06-24 13:45 ` Bagas Sanjaya [this message]
2025-06-25 14:00 ` ALOK TIWARI
2025-06-25 14:15 ` Bagas Sanjaya
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=f833718d-ea25-4e21-a103-4ee0153ca990@gmail.com \
--to=bagasdotme@gmail.com \
--cc=alok.a.tiwari@oracle.com \
--cc=corbet@lwn.net \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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;
as well as URLs for NNTP newsgroup(s).