From: Joe Perches <joe@perches.com>
To: Anup Patel <anup@brainfault.org>,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
KVM General <kvm@vger.kernel.org>,
linux-kselftest@vger.kernel.org,
linux-riscv <linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] KVM: selftests: riscv: Remove unneeded semicolon
Date: Sun, 08 May 2022 22:36:01 -0700 [thread overview]
Message-ID: <918affc0a0a91dab08647696ed6587021264f25f.camel@perches.com> (raw)
In-Reply-To: <CAAhSdy15CE5ZUROH-mOwhpR0AuwsK8h+8W-Kd0jxwsTixpQOQg@mail.gmail.com>
On Mon, 2022-05-09 at 10:37 +0530, Anup Patel wrote:
> On Fri, May 6, 2022 at 3:15 PM Jiapeng Chong
> <jiapeng.chong@linux.alibaba.com> wrote:
> >
> > Fix the following coccicheck warnings:
> >
> > ./tools/testing/selftests/kvm/lib/riscv/processor.c:353:3-4: Unneeded
> > semicolon.
> >
> > Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> > Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
>
> In future, please CC kvm-riscv@lists.infradead.org for KVM RISC-V related
> patches.
Perhaps add or update some MAINTAINERS entry as this list is not
currently specified by:
$ ./scripts/get_maintainer.pl -f tools/testing/selftests/kvm/lib/riscv/processor.c --nogit --nogit-fallback
Paolo Bonzini <pbonzini@redhat.com> (supporter:KERNEL VIRTUAL MACHINE (KVM))
Shuah Khan <shuah@kernel.org> (maintainer:KERNEL SELFTEST FRAMEWORK)
Paul Walmsley <paul.walmsley@sifive.com> (supporter:RISC-V ARCHITECTURE)
Palmer Dabbelt <palmer@dabbelt.com> (supporter:RISC-V ARCHITECTURE)
Albert Ou <aou@eecs.berkeley.edu> (supporter:RISC-V ARCHITECTURE)
kvm@vger.kernel.org (open list:KERNEL VIRTUAL MACHINE (KVM))
linux-kselftest@vger.kernel.org (open list:KERNEL SELFTEST FRAMEWORK)
linux-riscv@lists.infradead.org (open list:RISC-V ARCHITECTURE)
linux-kernel@vger.kernel.org (open list)
$
next prev parent reply other threads:[~2022-05-09 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 9:45 Jiapeng Chong
2022-05-09 5:07 ` Anup Patel
2022-05-09 5:36 ` Joe Perches [this message]
2022-05-09 5:47 ` Anup Patel
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=918affc0a0a91dab08647696ed6587021264f25f.camel@perches.com \
--to=joe@perches.com \
--cc=abaci@linux.alibaba.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
/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
all inboxes | Powered by JetHome®