From: Jens Axboe <axboe@kernel.dk>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [PATCH V3 0/3] null_blk: add tracepoints for zoned mode
Date: Fri, 27 Mar 2020 13:39:32 -0600 [thread overview]
Message-ID: <7ec7a6e6-01f9-8ff9-b1fb-9766b60ab979@kernel.dk> (raw)
In-Reply-To: <BYAPR04MB49659E6F0542900C9DFFE05A86CC0@BYAPR04MB4965.namprd04.prod.outlook.com>
On 3/27/20 1:35 PM, Chaitanya Kulkarni wrote:
> On 3/27/20 8:35 AM, Jens Axboe wrote:
>> On 3/26/20 9:12 PM, Chaitanya Kulkarni wrote:
>>> Hi Jens,
>>>
>>> Can we get this in ?
>> There still seems to be the unresolved issue of the function
>> declaration. I agree that we should not have a declaration for
>> a function if CONFIG_BLK_DEV_ZONED isn't set, so move it under
>> the existing ifdef.
>>
> Sorry for replying to previous series.
>
> Here is link for V4 which has above fix and Damien's review :-
>
> https://www.spinics.net/lists/linux-block/msg51305.html
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-03-27 19:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 2:16 [PATCH V3 0/3] null_blk: add tracepoints for zoned mode Chaitanya Kulkarni
2020-03-25 2:16 ` [PATCH V3 1/3] block: add a zone condition debug helper Chaitanya Kulkarni
2020-03-25 3:27 ` Damien Le Moal
2020-03-25 4:31 ` Chaitanya Kulkarni
2020-03-25 5:20 ` Damien Le Moal
2020-03-25 2:16 ` [PATCH V3 2/3] null_blk: add tracepoint helpers for zoned mode Chaitanya Kulkarni
2020-03-25 3:28 ` Damien Le Moal
2020-03-25 2:16 ` [PATCH V3 3/3] null_blk: add trace in null_blk_zoned.c Chaitanya Kulkarni
2020-03-27 3:12 ` [PATCH V3 0/3] null_blk: add tracepoints for zoned mode Chaitanya Kulkarni
2020-03-27 15:35 ` Jens Axboe
2020-03-27 16:05 ` Damien Le Moal
2020-03-27 16:25 ` Jens Axboe
2020-03-27 19:35 ` Chaitanya Kulkarni
2020-03-27 19:39 ` Jens Axboe [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=7ec7a6e6-01f9-8ff9-b1fb-9766b60ab979@kernel.dk \
--to=axboe@kernel.dk \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=linux-block@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).