From: Christoph Hellwig <hch@lst.de>
To: Shaun Tancheff <shaun.tancheff@seagate.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Damien Le Moal <damien.lemoal@hgst.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v2 7/7] blk-zoned: implement ioctls
Date: Tue, 27 Sep 2016 20:24:23 +0200 [thread overview]
Message-ID: <20160927182423.GA22238@lst.de> (raw)
In-Reply-To: <CAJVOszCdwMhLyZAJAWDnDBziyAejxdwi5J-X197RXwNuvC82GA@mail.gmail.com>
On Mon, Sep 26, 2016 at 06:12:24PM -0500, Shaun Tancheff wrote:
> Except our source locations are disjoint (stack and kcalloc'd).
Indeed.
next prev parent reply other threads:[~2016-09-27 18:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 11:14 [PATCH v2 0/7] ZBC / Zoned block device support Damien Le Moal
2016-09-26 11:14 ` [PATCH v2 1/7] block: Add 'zoned' queue limit Damien Le Moal
2016-09-27 21:09 ` Shaun Tancheff
2016-09-26 11:14 ` [PATCH v2 2/7] blk-sysfs: Add 'chunk_sectors' to sysfs attributes Damien Le Moal
2016-09-27 21:10 ` Shaun Tancheff
2016-09-26 11:14 ` [PATCH v2 3/7] block: update chunk_sectors in blk_stack_limits() Damien Le Moal
2016-09-27 21:12 ` Shaun Tancheff
2016-09-26 11:14 ` [PATCH v2 4/7] block: Define zoned block device operations Damien Le Moal
2016-09-26 11:14 ` [PATCH v2 5/7] block: Implement support for zoned block devices Damien Le Moal
2016-09-27 18:51 ` [PATCH v3 " Shaun Tancheff
2016-09-26 11:14 ` [PATCH v2 6/7] sd: Implement support for ZBC devices Damien Le Moal
2016-09-27 21:08 ` Shaun Tancheff
2016-09-26 11:14 ` [PATCH v2 7/7] blk-zoned: implement ioctls Damien Le Moal
2016-09-26 16:37 ` Christoph Hellwig
2016-09-26 23:12 ` Shaun Tancheff
2016-09-27 18:24 ` Christoph Hellwig [this message]
2016-09-26 23:30 ` Damien Le Moal
2016-09-26 23:58 ` Shaun Tancheff
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=20160927182423.GA22238@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@hgst.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=shaun.tancheff@seagate.com \
/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).