From: Segher Boessenkool <segher@kernel.crashing.org>
To: wangjianli <wangjianli@cdjrlc.com>
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Book3S HV:fix repeated words in comments
Date: Sun, 24 Jul 2022 20:43:33 -0500 [thread overview]
Message-ID: <20220725014333.GR25951@gate.crashing.org> (raw)
In-Reply-To: <20220724054137.58504-1-wangjianli@cdjrlc.com>
On Sun, Jul 24, 2022 at 01:41:37PM +0800, wangjianli wrote:
> From: Jianli Wang <wangjianli@cdjrlc.com>
>
> Delete the redundant word 'do'.
> - /* invalidate the entry (what do do on error from the above ?) */
> + /* invalidate the entry (what do on error from the above ?) */
Probably "what to do" was meant here?
Segher
prev parent reply other threads:[~2022-07-25 1:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 5:41 [PATCH] KVM: PPC: Book3S HV:fix repeated words in comments wangjianli
2022-07-25 1:43 ` Segher Boessenkool [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=20220725014333.GR25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=wangjianli@cdjrlc.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).