From: Chaitanya Kulkarni <kch@nvidia.com>
To: <linux-nvme@lists.infradead.org>
Cc: <hch@lst.de>, <sagi@grimberg.me>, <axboe@kernel.dk>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: [V2 0/3] nvmet: fix kernel-doc warnings
Date: Tue, 8 Mar 2022 21:59:24 -0800 [thread overview]
Message-ID: <20220309055927.11267-1-kch@nvidia.com> (raw)
Hi,
Fixes for kernel-doc warning for target.
-ck
V1 -> V2:-
1. Replace "compilation" with "kernel-doc" in commit message. (Jens)
Chaitanya Kulkarni (3):
nvmet-fc: fix kernel-doc warning for register
nvmet-fc: fix kernel-doc warning for unregitser
nvmet-rdma: fix kernel-doc warning
drivers/nvme/target/fc.c | 4 ++--
drivers/nvme/target/rdma.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.29.0
next reply other threads:[~2022-03-09 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 5:59 Chaitanya Kulkarni [this message]
2022-03-09 5:59 ` [V2 1/3] nvmet-fc: fix kernel-doc warning for register Chaitanya Kulkarni
2022-03-09 5:59 ` [V2 2/3] nvmet-fc: fix kernel-doc warning for unregitser Chaitanya Kulkarni
2022-03-09 5:59 ` [V2 3/3] nvmet-rdma: fix kernel-doc warning Chaitanya Kulkarni
2022-03-09 18:27 ` [V2 0/3] nvmet: fix kernel-doc warnings Christoph Hellwig
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=20220309055927.11267-1-kch@nvidia.com \
--to=kch@nvidia.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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