All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "roman.penyaev@profitbricks.com" <roman.penyaev@profitbricks.com>,
	"ming.lei@redhat.com" <ming.lei@redhat.com>
Cc: "hch@infradead.org" <hch@infradead.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"osandov@fb.com" <osandov@fb.com>, "axboe@fb.com" <axboe@fb.com>,
	"hare@suse.com" <hare@suse.com>
Subject: Re: [PATCH V2 0/2] block: remove unnecessary RESTART
Date: Mon, 30 Oct 2017 20:33:49 +0000	[thread overview]
Message-ID: <1509395628.27259.19.camel@wdc.com> (raw)
In-Reply-To: <CAJrWOzD0LoFhKhFf-BrCtWipVEteT3uUqUc30_qr8E8wNeESGg@mail.gmail.com>

T24gRnJpLCAyMDE3LTEwLTI3IGF0IDE5OjU1ICswMjAwLCBSb21hbiBQZW55YWV2IHdyb3RlOg0K
PiBUaGF0J3MganVzdCBhIGJ1ZyBpbiBjb2RlLCBub3QgYSBpbiBpc3N1ZSB3aXRoIHJlc3RhcnRz
LCB3aGljaCBjYW4gYmUgZml4ZWQNCj4gaWYgd2UgcHV0IGhjdHggd2hpY2ggYXJlIG5lZWRlZCB0
byBiZSByZXN0YXJ0ZWQgaW4gcGVyY3B1IGxpc3RzIGFuZCBhdm9pZA0KPiBsb25nIGxvb3BzIGFu
ZCBjb250ZW50aW9ucy4NCg0KSGVsbG8gUm9tYW4sDQoNCkhhdmUgeW91IG5vdGljZWQgdGhhdCBy
ZWNlbnRseSAuZ2V0X2J1ZGdldCgpIGFuZCAucHV0X2J1ZGdldCgpIGNhbGxiYWNrcyBoYXZlDQpi
ZWVuIGFkZGVkIGludG8gc3RydWN0IGJsa19tcV9vcHM/IElmIGJsb2NrIGRyaXZlcnMgdGhhdCBz
dXBwb3J0IHNoYXJlZCB0YWdzDQppbXBsZW1lbnQgdGhlc2UgY2FsbGJhY2sgZnVuY3Rpb25zIHBy
b3Blcmx5IHRoZW4gbWF5YmUgYnVzeSBjb25kaXRpb25zIGJlY29tZQ0KaW5mcmVxdWVudCBlbm91
Z2ggdG8gdXNlIGEgc2luZ2xlICJoY3R4IGJ1c3kiIGxpc3QgcGVyIHRhZyBzZXQgaW5zdGVhZCBv
Zg0KcGVyLWNwdSAiaGN0eCBidXN5IiBsaXN0cy4NCg0KQmFydC4=

  parent reply	other threads:[~2017-10-30 20:33 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27  4:43 [PATCH V2 0/2] block: remove unnecessary RESTART Ming Lei
2017-10-27  4:43 ` [PATCH V2 1/2] blk-mq: don't handle TAG_SHARED in restart Ming Lei
2017-10-27  4:43 ` [PATCH V2 2/2] blk-mq: don't restart queue when .get_budget returns BLK_STS_RESOURCE Ming Lei
2017-10-27  4:53 ` [PATCH V2 0/2] block: remove unnecessary RESTART Bart Van Assche
2017-10-27  5:38   ` Ming Lei
2017-10-27 17:55     ` Roman Penyaev
2017-10-28 15:47       ` Ming Lei
2017-10-30 20:33       ` Bart Van Assche [this message]
2017-11-01 16:55         ` Roman Penyaev
2017-10-30 20:24     ` Bart Van Assche
2017-10-31  1:47       ` Ming Lei
2017-11-01  3:54         ` Bart Van Assche
2017-11-01  4:08           ` Ming Lei
2017-11-01 16:47             ` Bart Van Assche
2017-11-01 16:59               ` Ming Lei
2017-11-01 17:09                 ` Bart Van Assche
2017-11-01 17:22                   ` Ming Lei
2017-10-31 20:29 ` Jens Axboe
2017-11-01  1:46   ` Ming Lei
2017-11-01  1:53     ` Jens Axboe
2017-11-01  2:03       ` Ming Lei
2017-11-01 14:21         ` Jens Axboe
2017-11-02 15:57           ` Bart Van Assche
2017-11-02 23:38             ` Ming Lei
2017-11-02 23:43               ` Bart Van Assche
2017-11-02 23:48                 ` Ming Lei
2017-11-02 23:54                   ` Bart Van Assche
2017-11-03  0:15                     ` Ming Lei
2017-11-03  0:48                       ` Bart Van Assche
2017-11-03  1:16                         ` Laurence Oberman
2017-11-03  2:12                           ` Ming Lei
2017-11-03  2:42                             ` Bart Van Assche
2017-11-03  3:50                               ` Ming Lei
2017-11-03 15:23                                 ` Bart Van Assche
2017-11-03 15:47                                   ` Ming Lei
2017-11-03 15:50                                     ` Bart Van Assche
2017-11-03 16:13                                       ` Laurence Oberman
2017-11-03 16:47                                         ` Ming Lei
2017-11-03 17:13                                           ` Laurence Oberman
2017-11-04  2:11                                           ` Ming Lei
2017-11-03 15:18                               ` Ming Lei
2017-11-03 15:43                                 ` Bart Van Assche
2017-11-03 15:47                                 ` Bart Van Assche

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=1509395628.27259.19.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=axboe@fb.com \
    --cc=hare@suse.com \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=osandov@fb.com \
    --cc=roman.penyaev@profitbricks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.