From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Luis Felipe Hernandez <luis.hernandez093@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
corbet@lwn.net
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mao Zhu <zhumao001@208suo.com>, Ran Sun <sunran001@208suo.com>,
Xiang wangx <wangxiang@cdjrlc.com>,
Shaomin Deng <dengshaomin@cdjrlc.com>,
Charles Han <hanchunchao@inspur.com>,
Attreyee M <tintinm2017@gmail.com>, LihaSika <lihasika@gmail.com>
Subject: Re: [PATCH] Refactor phrasing for clarity
Date: Mon, 13 May 2024 16:09:46 +0700 [thread overview]
Message-ID: <ZkHY2sYUOXVSWDMO@archie.me> (raw)
In-Reply-To: <20240513022430.17626-1-luis.hernandez093@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On Mon, May 13, 2024 at 02:24:02AM +0000, Luis Felipe Hernandez wrote:
> * Updated title capitalization for consistency
> * Fixed acronym capitalization (e.g. CPU, vCPU)
> * Added usage of hypenated compoud adjective
> (e.g. host-side polling, where host-side is modifying polling)
> * Added missing verb "as" in "basic logic is as follows"
> * Added missing articl "an" in "guest_halt_poll_ns when an event occurs"
> * Fixed parameter definition in 4, all previous examples started with
> descibing the parameter in the first sentence followed by additional
> notes
> * Replaced C-terminology Bool in favor of formal form Boolean
> * Cleaned up phrasing in "Further Notes" section for clarity
>
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-05-13 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 2:24 [PATCH] Refactor phrasing for clarity Luis Felipe Hernandez
2024-05-13 9:09 ` Bagas Sanjaya [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=ZkHY2sYUOXVSWDMO@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dengshaomin@cdjrlc.com \
--cc=hanchunchao@inspur.com \
--cc=lihasika@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.hernandez093@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=sunran001@208suo.com \
--cc=tintinm2017@gmail.com \
--cc=wangxiang@cdjrlc.com \
--cc=zhumao001@208suo.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 read-only IMAP folder(s) and NNTP newsgroup(s).