[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f83cacb8-de44-05b9-dfbc-73e1d5ed02e2@deltatee.com>
Date: Wed, 14 Aug 2019 10:59:44 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Max Gurtovoy <maxg@...lanox.com>, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-block@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Cc: Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>,
Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@....com>,
Stephen Bates <sbates@...thlin.com>
Subject: Re: [PATCH v7 03/14] nvmet: add return value to
nvmet_add_async_event()
On 2019-08-14 8:26 a.m., Max Gurtovoy wrote:
>
> On 8/2/2019 2:45 AM, Logan Gunthorpe wrote:
>> From: Chaitanya Kulkarni <chaitanya.kulkarni@....com>
>>
>> Change the return value for nvmet_add_async_event().
>>
>> This change is needed for the target passthru code to generate async
>> events.
>
> As a stand alone commit it's not clear what is the purpose of it.
>
> Please add some extra explanation in the commit message.
>
> Also better to use integer as return value if the return value should
> reflect return code.
Thanks for the Review, Max. I'll queue up these changes for v8.
Logan
Powered by blists - more mailing lists