public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	Chaitanya Kulkarni <chaitanyak@nvidia.com>
Subject: Re: [PATCH 0/3] nvmet: fix compilation warnings
Date: Wed, 9 Mar 2022 04:15:23 +0000	[thread overview]
Message-ID: <4c24edbd-bf1c-8918-422f-b0d19e202398@nvidia.com> (raw)
In-Reply-To: <ec24258c-6e52-8ff0-2cd0-ac25de35bca8@kernel.dk>

On 3/8/22 15:33, Jens Axboe wrote:
> 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.

Okay will send out v2, thanks.

-ck



      reply	other threads:[~2022-03-09  4:16 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 ` [PATCH 0/3] nvmet: fix compilation warnings Jens Axboe
2022-03-09  4:15   ` Chaitanya Kulkarni [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=4c24edbd-bf1c-8918-422f-b0d19e202398@nvidia.com \
    --to=chaitanyak@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