From: Paolo Bonzini <pbonzini@redhat.com>
To: ChenXiaoSong <chenxiaosong2@huawei.com>,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
x86@kernel.org
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
yukuai3@huawei.com, yi.zhang@huawei.com
Subject: Re: [PATCH -next] KVM: SVM: fix doc warnings
Date: Thu, 10 Jun 2021 13:47:27 +0200 [thread overview]
Message-ID: <7541d362-253a-5a56-1716-1ca9ef33cbae@redhat.com> (raw)
In-Reply-To: <20210609122217.2967131-1-chenxiaosong2@huawei.com>
On 09/06/21 14:22, ChenXiaoSong wrote:
> Fix gcc W=1 warnings:
These are not gcc W=1 warnings, they are kernel-doc warnings. Anyway,
patch queued---thanks!
Paolo
> arch/x86/kvm/svm/avic.c:233: warning: Function parameter or member 'activate' not described in 'avic_update_access_page'
> arch/x86/kvm/svm/avic.c:233: warning: Function parameter or member 'kvm' not described in 'avic_update_access_page'
> arch/x86/kvm/svm/avic.c:781: warning: Function parameter or member 'e' not described in 'get_pi_vcpu_info'
> arch/x86/kvm/svm/avic.c:781: warning: Function parameter or member 'kvm' not described in 'get_pi_vcpu_info'
> arch/x86/kvm/svm/avic.c:781: warning: Function parameter or member 'svm' not described in 'get_pi_vcpu_info'
> arch/x86/kvm/svm/avic.c:781: warning: Function parameter or member 'vcpu_info' not described in 'get_pi_vcpu_info'
> arch/x86/kvm/svm/avic.c:1009: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
>
> Signed-off-by: ChenXiaoSong<chenxiaosong2@huawei.com>
> ---
> arch/x86/kvm/svm/avic.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
prev parent reply other threads:[~2021-06-10 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 12:22 [PATCH -next] KVM: SVM: fix doc warnings ChenXiaoSong
2021-06-10 11:47 ` Paolo Bonzini [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=7541d362-253a-5a56-1716-1ca9ef33cbae@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=chenxiaosong2@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.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).