All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Valente <paolo.valente@linaro.org>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
	"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"bfq-iosched@googlegroups.com" <bfq-iosched@googlegroups.com>,
	"oleksandr@natalenko.name" <oleksandr@natalenko.name>
Subject: Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge
Date: Mon, 14 May 2018 19:16:54 +0200	[thread overview]
Message-ID: <8B9DC3A2-0DB0-4EEB-AFB2-C4D6560B7A4A@linaro.org> (raw)
In-Reply-To: <d534de4765c0fbcc7bcd858c1d2f40391ece19ac.camel@wdc.com>



> Il giorno 10 mag 2018, alle ore 18:14, Bart Van Assche =
<bart.vanassche@wdc.com> ha scritto:
>=20
> On Fri, 2018-05-04 at 19:17 +0200, Paolo Valente wrote:
>> When invoked for an I/O request rq, [ ... ]
>=20
> Tested-by: Bart Van Assche <bart.vanassche@wdc.com>
>=20
>=20
>=20

Any decision for this fix, Jens?

Thanks,
Paolo=

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Valente <paolo.valente@linaro.org>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
	"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"bfq-iosched@googlegroups.com" <bfq-iosched@googlegroups.com>,
	"oleksandr@natalenko.name" <oleksandr@natalenko.name>
Subject: Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge
Date: Mon, 14 May 2018 19:16:54 +0200	[thread overview]
Message-ID: <8B9DC3A2-0DB0-4EEB-AFB2-C4D6560B7A4A@linaro.org> (raw)
In-Reply-To: <d534de4765c0fbcc7bcd858c1d2f40391ece19ac.camel@wdc.com>



> Il giorno 10 mag 2018, alle ore 18:14, Bart Van Assche <bart.vanassche@wdc.com> ha scritto:
> 
> On Fri, 2018-05-04 at 19:17 +0200, Paolo Valente wrote:
>> When invoked for an I/O request rq, [ ... ]
> 
> Tested-by: Bart Van Assche <bart.vanassche@wdc.com>
> 
> 
> 

Any decision for this fix, Jens?

Thanks,
Paolo

  reply	other threads:[~2018-05-14 17:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 17:17 [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge Paolo Valente
2018-05-04 19:46 ` Mike Galbraith
2018-05-05  8:19   ` Mike Galbraith
2018-05-05 10:39     ` Paolo Valente
2018-05-05 10:39       ` Paolo Valente
2018-05-05 14:56       ` Mike Galbraith
2018-05-05 14:56         ` Mike Galbraith
2018-05-06  7:42         ` Paolo Valente
2018-05-06  7:42           ` Paolo Valente
2018-05-07  2:43           ` Mike Galbraith
2018-05-07  2:43             ` Mike Galbraith
2018-05-07  3:23             ` Mike Galbraith
2018-05-07  3:23               ` Mike Galbraith
2018-05-07  9:32               ` Paolo Valente
2018-05-07  9:32                 ` Paolo Valente
2018-05-07  5:56           ` Mike Galbraith
2018-05-07  5:56             ` Mike Galbraith
2018-05-07  9:27             ` Paolo Valente
2018-05-07  9:27               ` Paolo Valente
2018-05-07 10:01               ` Mike Galbraith
2018-05-07 10:01                 ` Mike Galbraith
2018-05-07 18:03                 ` Paolo Valente
2018-05-07 18:03                   ` Paolo Valente
2018-05-06  7:33 ` Oleksandr Natalenko
2018-05-10 16:14 ` Bart Van Assche
2018-05-10 16:14   ` Bart Van Assche
2018-05-14 17:16   ` Paolo Valente [this message]
2018-05-14 17:16     ` Paolo Valente
2018-05-14 17:31     ` Jens Axboe
2018-05-14 17:37       ` Paolo Valente
2018-05-14 17:37         ` Paolo Valente

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=8B9DC3A2-0DB0-4EEB-AFB2-C4D6560B7A4A@linaro.org \
    --to=paolo.valente@linaro.org \
    --cc=axboe@kernel.dk \
    --cc=bart.vanassche@wdc.com \
    --cc=bfq-iosched@googlegroups.com \
    --cc=broonie@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksandr@natalenko.name \
    --cc=ulf.hansson@linaro.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 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.