From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "hch@lst.de" <hch@lst.de>,
"jianchao.w.wang@oracle.com" <jianchao.w.wang@oracle.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"israelr@mellanox.com" <israelr@mellanox.com>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"sebott@linux.ibm.com" <sebott@linux.ibm.com>,
"ming.lei@redhat.com" <ming.lei@redhat.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"maxg@mellanox.com" <maxg@mellanox.com>,
"tj@kernel.org" <tj@kernel.org>
Subject: Re: [PATCH] blk-mq: Rework blk-mq timeout handling again
Date: Mon, 14 May 2018 04:03:43 +0000 [thread overview]
Message-ID: <4f773949c3e32a9d65ab09159fb7b6988349e91b.camel@wdc.com> (raw)
In-Reply-To: <beab60f7-5fee-f1d8-12c3-c43d005d6427@oracle.com>
T24gTW9uLCAyMDE4LTA1LTE0IGF0IDA5OjM3ICswODAwLCBqaWFuY2hhby53YW5nIHdyb3RlOg0K
PiBJbiBhZGRpdGlvbiwgb24gYSA2NGJpdCBzeXN0ZW0sIGhvdyBkbyB5b3Ugc2V0IHVwIHRoZSB0
aW1lciB3aXRoIGEgMzJiaXQgZGVhZGxpbmUgPw0KDQpJZiB0aW1lb3V0IGhhbmRsaW5nIG9jY3Vy
cyBsZXNzIHRoYW4gKDEgPDwgMzEpIC8gSFogc2Vjb25kcyBhZnRlciBhIHJlcXVlc3QgaGFzIGJl
ZW4NCnN1Ym1pdHRlZCB0aGVuIGEgMzItYml0IHZhcmlhYmxlIGlzIHN1ZmZpY2llbnQgdG8gc3Rv
cmUgdGhlIGRlYWRsaW5lLiBJZiB5b3Ugd2FudCB0bw0KdmVyaWZ5IHRoZSBpbXBsZW1lbnRhdGlv
biwgcGxlYXNlIGhhdmUgYSBsb29rIGF0IHRoZSBpbnQzMl90IHZhcmlhYmxlcyBpbg0KYmxrX21x
X2NoZWNrX2V4cGlyZWQoKS4NCg0KQmFydC4NCg0KDQo=
next prev parent reply other threads:[~2018-05-14 4:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 17:56 [PATCH] blk-mq: Rework blk-mq timeout handling again Bart Van Assche
2018-05-11 12:06 ` jianchao.wang
2018-05-11 12:35 ` Christoph Hellwig
2018-05-11 15:29 ` Bart Van Assche
2018-05-14 1:37 ` jianchao.wang
2018-05-14 4:03 ` Bart Van Assche [this message]
2018-05-14 5:15 ` jianchao.wang
2018-05-14 18:44 ` Bart Van Assche
2018-05-11 15:26 ` Bart Van Assche
2018-05-14 1:48 ` jianchao.wang
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=4f773949c3e32a9d65ab09159fb7b6988349e91b.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=israelr@mellanox.com \
--cc=jianchao.w.wang@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=maxg@mellanox.com \
--cc=ming.lei@redhat.com \
--cc=sagi@grimberg.me \
--cc=sebott@linux.ibm.com \
--cc=tj@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