From: Mike Snitzer <snitzer@redhat.com>
To: sfr@canb.auug.org.au, linux-next@vger.kernel.org
Cc: Ming Lei <ming.lei@canonical.com>, Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: next-20150313's block is broken, but fix available [was: Re: block: fully initialize queue in blk_mq_init_allocated_queue]
Date: Fri, 13 Mar 2015 10:17:22 -0400 [thread overview]
Message-ID: <20150313141722.GA13425@redhat.com> (raw)
In-Reply-To: <20150313123709.GA430@swordfish>
On Fri, Mar 13 2015 at 8:37am -0400,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com> wrote:
> On (03/13/15 08:24), Mike Snitzer wrote:
> > Thanks, but I already fixed these 2 patches and pushed them to
> > linux-dm.git's for-next branch last night (I also posted v3 of the
> > corresponding patches to LKML at that time).
>
> oh, I see. didn't know that.
>
> > Sorry to waste your time, I've learned my lesson:
> >
>
> no problem.
>
> > Hopefully linux-next was able to pick up my new 'for-next' and we don't
> > have an entire weekend of linux-next crashes due to my idiocy.
>
> nope, this is how I spot it -- next-20150313 doesn't boot.
Hi Stephen,
Is there any opportunity to get the tree fixed by re-pulling
linux-dm.git's 'for-next'? I'd hate to kill linux-next productivity
this weekend! Sorry about this.
Please advise, thanks.
Mike
prev parent reply other threads:[~2015-03-13 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 9:30 [PATCH] block: fully initialize queue in blk_mq_init_allocated_queue Sergey Senozhatsky
2015-03-13 12:24 ` Mike Snitzer
2015-03-13 12:37 ` Sergey Senozhatsky
2015-03-13 14:17 ` Mike Snitzer [this message]
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=20150313141722.GA13425@redhat.com \
--to=snitzer@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=sfr@canb.auug.org.au \
/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.