From: Paolo Valente <paolo.valente@linaro.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Mark Brown <broonie@kernel.org>,
linus.walleij@linaro.org, bfq-iosched@googlegroups.com,
oleksandr@natalenko.name
Subject: Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge
Date: Mon, 7 May 2018 20:03:10 +0200 [thread overview]
Message-ID: <A25FE1D8-71DF-4781-A0A6-67DDD0AB5C44@linaro.org> (raw)
In-Reply-To: <1525687297.26987.1.camel@gmx.de>
> Il giorno 07 mag 2018, alle ore 12:01, Mike Galbraith <efault@gmx.de> =
ha scritto:
>=20
> On Mon, 2018-05-07 at 11:27 +0200, Paolo Valente wrote:
>>=20
>>=20
>> Where is the bug?
>=20
> Hm, seems potent pain-killers and C don't mix all that well.
>=20
I'll try to keep it in mind, and I do wis you to get well soon.
Thanks,
Paolo=
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Valente <paolo.valente@linaro.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Mark Brown <broonie@kernel.org>,
linus.walleij@linaro.org, bfq-iosched@googlegroups.com,
oleksandr@natalenko.name
Subject: Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge
Date: Mon, 7 May 2018 20:03:10 +0200 [thread overview]
Message-ID: <A25FE1D8-71DF-4781-A0A6-67DDD0AB5C44@linaro.org> (raw)
In-Reply-To: <1525687297.26987.1.camel@gmx.de>
> Il giorno 07 mag 2018, alle ore 12:01, Mike Galbraith <efault@gmx.de> ha scritto:
>
> On Mon, 2018-05-07 at 11:27 +0200, Paolo Valente wrote:
>>
>>
>> Where is the bug?
>
> Hm, seems potent pain-killers and C don't mix all that well.
>
I'll try to keep it in mind, and I do wis you to get well soon.
Thanks,
Paolo
next prev parent reply other threads:[~2018-05-07 18:03 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 [this message]
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
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=A25FE1D8-71DF-4781-A0A6-67DDD0AB5C44@linaro.org \
--to=paolo.valente@linaro.org \
--cc=axboe@kernel.dk \
--cc=bfq-iosched@googlegroups.com \
--cc=broonie@kernel.org \
--cc=efault@gmx.de \
--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.