Return-path: Received: from mx1.redhat.com ([209.132.183.28]:61189 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753460AbaARHTI (ORCPT ); Sat, 18 Jan 2014 02:19:08 -0500 Date: Sat, 18 Jan 2014 08:15:38 +0100 From: Alexander Gordeev To: Bjorn Helgaas Cc: "linux-kernel@vger.kernel.org" , Brian King , Tejun Heo , Matthew Wilcox , Alex Williamson , Kalle Valo , Vladimir Kondratiev , linux-wireless , wil6210@qca.qualcomm.com, ath10k@lists.infradead.org, linux-nvme@lists.infradead.org, "linux-ide@vger.kernel.org" , "linux-scsi@vger.kernel.org" , "kvm@vger.kernel.org" , "linux-pci@vger.kernel.org" Subject: Re: [PATCH v2 0/9] Phase out pci_enable_msi_block() Message-ID: <20140118071538.GA32535@dhcp-26-207.brq.redhat.com> (sfid-20140118_081921_508643_63B29983) References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, Jan 17, 2014 at 02:00:32PM -0700, Bjorn Helgaas wrote: > > As the release is supposedly this weekend, do you prefer > > the patches to go to your tree or to individual trees after > > the release? > > I'd be happy to merge them, except for the fact that they probably > wouldn't have any time in -next before I ask Linus to pull them. So > how about if we wait until after the release, ask the area maintainers > to take them, and if they don't take them, I'll put them in my tree > for v3.15? Patch 11 depends on patches 1-10, so I am not sure how to better handle it. Whatever works for you ;) I am only concerned with a regression fix "ahci: Fix broken fallback to single MSI mode" which would be nice to have in 3.14. But it seems pretty much too late. > Bjorn Thanks! -- Regards, Alexander Gordeev agordeev@redhat.com