From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Damien Le Moal <damien.lemoal@wdc.com>,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
Bart Van Assche <Bart.VanAssche@wdc.com>
Subject: Re: [PATCH V9 0/7] blk-mq support for ZBC disks
Date: Mon, 08 Jan 2018 22:14:31 -0500 [thread overview]
Message-ID: <yq1bmi3oh9k.fsf@oracle.com> (raw)
In-Reply-To: <76006cca-d93f-4bc6-6408-fb86d7470dcc@kernel.dk> (Jens Axboe's message of "Mon, 8 Jan 2018 09:07:56 -0700")
Jens,
> Completely up to you - I already have 1-5, I can add 6/7 as well, or
> just can do it in your tree. Let me know what you prefer.
Started my 4.16/scsi-fixes branch early based on your tree.
I queued these two up.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-01-09 3:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 6:43 [PATCH V9 0/7] blk-mq support for ZBC disks Damien Le Moal
2017-12-21 6:43 ` [PATCH V9 1/7] block: introduce zoned block devices zone write locking Damien Le Moal
2017-12-21 6:43 ` [PATCH V9 2/7] mq-deadline: Introduce dispatch helpers Damien Le Moal
2017-12-21 6:43 ` [PATCH V9 3/7] mq-deadline: Introduce zone locking support Damien Le Moal
2017-12-21 6:43 ` [PATCH V9 4/7] deadline-iosched: Introduce dispatch helpers Damien Le Moal
2017-12-21 6:43 ` [PATCH V9 5/7] deadline-iosched: Introduce zone locking support Damien Le Moal
2017-12-21 6:43 ` [PATCH V9 6/7] sd_zbc: Initialize device request queue zoned data Damien Le Moal
2017-12-21 6:43 ` [PATCH V9 7/7] sd: Remove zone write locking Damien Le Moal
2018-01-05 16:21 ` [PATCH V9 0/7] blk-mq support for ZBC disks Jens Axboe
2018-01-08 15:52 ` Martin K. Petersen
2018-01-08 16:07 ` Jens Axboe
2018-01-09 3:14 ` Martin K. Petersen [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=yq1bmi3oh9k.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Bart.VanAssche@wdc.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@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