All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Jiang Jian <jiangjian@cdjrlc.com>,
	borntraeger@linux.ibm.com, imbrenda@linux.ibm.com
Cc: david@redhat.com, hca@linux.ibm.com, gor@linux.ibm.com,
	agordeev@linux.ibm.com, svens@linux.ibm.com, kvm@vger.kernel.org,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: s390: drop unexpected word 'and' in the comments
Date: Thu, 23 Jun 2022 08:34:13 +0200	[thread overview]
Message-ID: <afee9027-1c4d-5c9c-8726-0b751cc13f46@linux.ibm.com> (raw)
In-Reply-To: <20220622140720.7617-1-jiangjian@cdjrlc.com>

On 6/22/22 16:07, Jiang Jian wrote:
> there is an unexpected word 'and' in the comments that need to be dropped
> 
> file: arch/s390/kvm/interrupt.c
> line: 705
> 
> * Subsystem damage are the only two and and are indicated by
> 
> changed to:
> 
> * Subsystem damage are the only two and are indicated by
> 
> Signed-off-by: Jiang Jian <jiangjian@cdjrlc.com>

Thanks, queued

> ---
>   arch/s390/kvm/interrupt.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/s390/kvm/interrupt.c b/arch/s390/kvm/interrupt.c
> index af96dc0549a4..1e3fb2d4d448 100644
> --- a/arch/s390/kvm/interrupt.c
> +++ b/arch/s390/kvm/interrupt.c
> @@ -702,7 +702,7 @@ static int __must_check __deliver_machine_check(struct kvm_vcpu *vcpu)
>   	/*
>   	 * We indicate floating repressible conditions along with
>   	 * other pending conditions. Channel Report Pending and Channel
> -	 * Subsystem damage are the only two and and are indicated by
> +	 * Subsystem damage are the only two and are indicated by
>   	 * bits in mcic and masked in cr14.
>   	 */
>   	if (test_and_clear_bit(IRQ_PEND_MCHK_REP, &fi->pending_irqs)) {


      reply	other threads:[~2022-06-23  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 14:07 [PATCH] KVM: s390: drop unexpected word 'and' in the comments Jiang Jian
2022-06-23  6:34 ` Janosch Frank [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=afee9027-1c4d-5c9c-8726-0b751cc13f46@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=jiangjian@cdjrlc.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=svens@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.