From: Dan Carpenter <dan.carpenter@oracle.com>
To: Ajay Joshi <Ajay.Joshi@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [bug report] null_blk: return fixed zoned reads > write pointer
Date: Mon, 28 Oct 2019 09:13:42 +0300 [thread overview]
Message-ID: <20191028061342.GA1922@kadam> (raw)
In-Reply-To: <CY4PR04MB3719FA7043998B66D0E35BBA8F660@CY4PR04MB3719.namprd04.prod.outlook.com>
Argh... Sorry. No, I just read the code badly. Forget about it.
regards,
dan carpenter
prev parent reply other threads:[~2019-10-28 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 13:06 [bug report] null_blk: return fixed zoned reads > write pointer Dan Carpenter
2019-10-25 20:25 ` Jens Axboe
2019-10-28 4:40 ` Ajay Joshi
2019-10-28 6:13 ` Dan Carpenter [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=20191028061342.GA1922@kadam \
--to=dan.carpenter@oracle.com \
--cc=Ajay.Joshi@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).