From: Jens Axboe <axboe@kernel.dk>
To: Chaitanya Kulkarni <kch@nvidia.com>, linux-nvme@lists.infradead.org
Cc: hch@lst.de, sagi@grimberg.me
Subject: Re: [PATCH 0/3] nvmet: fix compilation warnings
Date: Tue, 8 Mar 2022 16:33:30 -0700 [thread overview]
Message-ID: <ec24258c-6e52-8ff0-2cd0-ac25de35bca8@kernel.dk> (raw)
In-Reply-To: <20220308230022.8863-1-kch@nvidia.com>
On 3/8/22 4:00 PM, Chaitanya Kulkarni wrote:
> Hi,
>
> Fixes for compilation warning for target.
>
> -ck
>
> Chaitanya Kulkarni (3):
> nvmet-fc: fix compilation warning for register
> nvmet-fc: fix compilation warning for unregitser
> nvmet-rdma: fix compilation warning
Nit - these are kerneldoc warnings, they are not compilation warnings. I
would reword those commits.
--
Jens Axboe
next prev parent reply other threads:[~2022-03-08 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 23:00 [PATCH 0/3] nvmet: fix compilation warnings Chaitanya Kulkarni
2022-03-08 23:00 ` [PATCH 1/3] nvmet-fc: fix compilation warning for register Chaitanya Kulkarni
2022-03-08 23:00 ` [PATCH 2/3] nvmet-fc: fix compilation warning for unregitser Chaitanya Kulkarni
2022-03-08 23:00 ` [PATCH 3/3] nvmet-rdma: fix compilation warning Chaitanya Kulkarni
2022-03-08 23:33 ` Jens Axboe [this message]
2022-03-09 4:15 ` [PATCH 0/3] nvmet: fix compilation warnings Chaitanya Kulkarni
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=ec24258c-6e52-8ff0-2cd0-ac25de35bca8@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--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