Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751853AbaGGSec (ORCPT ); Mon, 7 Jul 2014 14:34:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:63903 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750869AbaGGSea (ORCPT ); Mon, 7 Jul 2014 14:34:30 -0400 Date: Mon, 7 Jul 2014 20:03:25 +0200 From: Alexander Gordeev To: Bjorn Helgaas Cc: James Bottomley , "DL-MPTFusionLinux@lsi.com" , "linux-kernel@vger.kernel.org" , "intel-linux-scu@intel.com" , "iss_storagedev@hp.com" , "linux-scsi@vger.kernel.org" , "pv-drivers@vmware.com" , "qla2xxx-upstream@qlogic.com" , "linux-pci@vger.kernel.org" , "support@lsi.com" , "iscsi-driver@qlogic.com" Subject: Re: [PATCH v2 RESEND 00/23] scsi: Use pci_enable_msix_range() instead of pci_enable_msix() Message-ID: <20140707180324.GA23039@dhcp-26-207.brq.redhat.com> References: <20140424170903.GA29593@google.com> <1398361868.6766.0.camel@dabdike> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 24, 2014 at 12:07:12PM -0600, Bjorn Helgaas wrote: > >> These depend on f7fc32c, which appeared in v3.15-rc1. I had intended > >> to merge these scsi updates at the same time, but I failed. Would you > >> like to take them now that f7fc32c is upstream? > > > > OK, will add them. I'm planning to base the scsi-misc tree on -rc3 once > > we have our current crop of fixes upstream. > > Great, thanks! James, Bjorn, All patches except 'be2iscsi' (patch 1) and 'hpsa' (patches 9,10) still apply. Would you take those apply or have me resend all of them or just 'be2iscsi' and 'hpsa'? Thanks! > Bjorn -- Regards, Alexander Gordeev agordeev@redhat.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/