From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755010AbbCMMgz (ORCPT ); Fri, 13 Mar 2015 08:36:55 -0400 Received: from mail-pa0-f48.google.com ([209.85.220.48]:38683 "EHLO mail-pa0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753444AbbCMMgw (ORCPT ); Fri, 13 Mar 2015 08:36:52 -0400 Date: Fri, 13 Mar 2015 21:37:10 +0900 From: Sergey Senozhatsky To: Mike Snitzer Cc: Sergey Senozhatsky , Ming Lei , Jens Axboe , linux-kernel@vger.kernel.org Subject: Re: block: fully initialize queue in blk_mq_init_allocated_queue Message-ID: <20150313123709.GA430@swordfish> References: <1426239050-2528-1-git-send-email-sergey.senozhatsky@gmail.com> <20150313122436.GB7312@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150313122436.GB7312@redhat.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. thanks, -ss