Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Oliver Upton <oliver.upton@linux.dev>, kvmarm@lists.linux.dev
Cc: Zenghui Yu <yuzenghui@huawei.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Marc Zyngier <maz@kernel.org>,
	kvm@vger.kernel.org, James Morse <james.morse@arm.com>,
	Jing Zhang <jingzhangos@google.com>
Subject: Re: [PATCH] KVM: arm64: Don't use kerneldoc comment for arm64_check_features()
Date: Mon, 18 Sep 2023 17:14:50 +0000	[thread overview]
Message-ID: <169505728619.3220441.6873711747214008692.b4-ty@linux.dev> (raw)
In-Reply-To: <20230913165645.2319017-1-oliver.upton@linux.dev>

On Wed, 13 Sep 2023 16:56:44 +0000, Oliver Upton wrote:
> A double-asterisk opening mark to the comment (i.e. '/**') indicates a
> comment block is in the kerneldoc format. There's automation in place to
> validate that kerneldoc blocks actually adhere to the formatting rules.
> 
> The function comment for arm64_check_features() isn't kerneldoc; use a
> 'regular' comment to silence automation warnings.
> 
> [...]

Applied to kvmarm/next, thanks!

[1/1] KVM: arm64: Don't use kerneldoc comment for arm64_check_features()
      https://git.kernel.org/kvmarm/kvmarm/c/7b424ffcd458

--
Best,
Oliver

      parent reply	other threads:[~2023-09-18 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 16:56 [PATCH] KVM: arm64: Don't use kerneldoc comment for arm64_check_features() Oliver Upton
2023-09-13 17:27 ` Jing Zhang
2023-09-18 12:56 ` Zenghui Yu
2023-09-18 17:14 ` Oliver Upton [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=169505728619.3220441.6873711747214008692.b4-ty@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=james.morse@arm.com \
    --cc=jingzhangos@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=maz@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=yuzenghui@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