From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <bvanassche@acm.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: Upcoming merge window
Date: Mon, 17 Dec 2018 16:27:38 -0700 [thread overview]
Message-ID: <8ae21d8c-81a1-891a-66c4-c94ff8bee20b@kernel.dk> (raw)
In-Reply-To: <1545088576.185366.443.camel@acm.org>
On 12/17/18 4:16 PM, Bart Van Assche wrote:
> On Mon, 2018-12-17 at 11:28 -0700, Jens Axboe wrote:
>> As I'm sure you're all aware, the merge window is coming up. This time
>> it happens to coincide with that is a holiday for most. My plan is to
>> send in an EARLY pull request to Linus, Thursday at the latest. If you're
>> sitting on anything that should go in with the initial merge, then I need
>> to have it ASAP.
>>
>> I'll do a later pull about a week in with things that were missed, but
>> I'm really hoping to make that fixes only. Any driver updates etc should
>> go in now.
>
> Hi Jens,
>
> If I run blktests/srp/002 against Linus' master branch then that test passes,
> no matter how many times I run that test. If I run that test against your
> for-next branch however (commit 6a252f2772c0) then that test hangs. The output
> of my list-pending-block-requests script is as follows when the hang occurs:
Ugh, I'll try and run that here again, that test is unfortunately such a pain
to run and requires me to manually install multipath libs (and remember to
uninstall before rebooting, or udev fails?).
I'll take a look!
--
Jens Axboe
next prev parent reply other threads:[~2018-12-17 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 18:28 Upcoming merge window Jens Axboe
2018-12-17 23:16 ` Bart Van Assche
2018-12-17 23:27 ` Jens Axboe [this message]
2018-12-17 23:49 ` Jens Axboe
2018-12-18 0:16 ` Jens Axboe
2018-12-18 0:26 ` Jens Axboe
2018-12-18 3:45 ` Mike Snitzer
2018-12-18 4:13 ` Jens Axboe
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=8ae21d8c-81a1-891a-66c4-c94ff8bee20b@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=linux-block@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