From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Jens Axboe <axboe@kernel.dk>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH V3 0/3] null_blk: add tracepoints for zoned mode
Date: Fri, 27 Mar 2020 16:05:30 +0000 [thread overview]
Message-ID: <CO2PR04MB2343F7076EE9192F1015C34FE7CC0@CO2PR04MB2343.namprd04.prod.outlook.com> (raw)
In-Reply-To: 093c4ab1-924f-b109-31a8-ce5813f52e14@kernel.dk
On 2020/03/28 0:35, 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.
The latest v4 series that Chaitanya posted addressed this issue.
The subject of this email is indeed v3 though...
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2020-03-27 16:05 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 [this message]
2020-03-27 16:25 ` Jens Axboe
2020-03-27 19:35 ` Chaitanya Kulkarni
2020-03-27 19:39 ` Jens Axboe
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=CO2PR04MB2343F7076EE9192F1015C34FE7CC0@CO2PR04MB2343.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=axboe@kernel.dk \
--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).