From: Dan Carpenter <dan.carpenter@linaro.org>
To: Afkari Zergaw <afkarizergaw12@gmail.com>
Cc: marvin24@gmx.de, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: KVM: fix punctuation for e.g. and i.e.
Date: Mon, 2 Mar 2026 11:49:56 +0300 [thread overview]
Message-ID: <aaVPNNUL_IdbkX4a@stanley.mountain> (raw)
In-Reply-To: <20260302013610.3815-1-afkarizergaw12@gmail.com>
On Mon, Mar 02, 2026 at 01:36:09AM +0000, Afkari Zergaw wrote:
> Add missing commas after "e.g." and "i.e." in the KVM API
> documentation to improve readability and follow standard
> punctuation usage.
>
> Signed-off-by: Afkari Zergaw <afkarizergaw12@gmail.com>
> ---
> Documentation/virt/kvm/api.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index fc5736839edd..c8500f0e913a 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -6346,12 +6346,12 @@ A KVM_MEM_GUEST_MEMFD region _must_ have a valid guest_memfd (private memory) an
> userspace_addr (shared memory). However, "valid" for userspace_addr simply
> means that the address itself must be a legal userspace address. The backing
> mapping for userspace_addr is not required to be valid/populated at the time of
> -KVM_SET_USER_MEMORY_REGION2, e.g. shared memory can be lazily mapped/allocated
> +KVM_SET_USER_MEMORY_REGION2, e.g., shared memory can be lazily mapped/allocated
> on-demand.
Google says this is an America vs Britain thing.
regards,
dan carpenter
next prev parent reply other threads:[~2026-03-02 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 1:36 [PATCH] Documentation: KVM: fix punctuation for e.g. and i.e Afkari Zergaw
2026-03-02 1:44 ` Greg KH
2026-03-02 8:49 ` Dan Carpenter [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-01 8:18 Afkari Zergaw
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=aaVPNNUL_IdbkX4a@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=afkarizergaw12@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
/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