| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 23 Feb 2014 20:45:49 +0100 From: Alexander Gordeev <agordeev@...hat.com> To: James Smart <james.smart@...lex.Com> Cc: linux-scsi@...r.kernel.org, linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 12/22] lpfc: Use pci_enable_msix_range() On Thu, Feb 20, 2014 at 11:47:02AM -0500, James Smart wrote: > Alexander, > > I've reworked this patch to layer on top of our rev 8.3.45 patches > that were just posted to linux-scsi. There were some conflicts due to > new additions. Additionally, there were two other uses of pci_enable_msiXXX > that needed to be addressed. The changes in this patch also address the > change requested by: > "[PATCH 11/22] lpfc: Remove superfluous call to pci_disable_msix()" > > To avoid creating merge conflicts - either by your patches going in then > scsi git tree trying to merge or by scsi git tree going in and your patches > trying to merge - I recommend that you eliminate your lpfc patches from the > kernel and apply the patch below once scsi git with the updated lpfc driver > has actually merged. Hi James, Thank you for the review and for the updated patch - it is embarrassing I have not addressed all pci_enable_msix()'s. I will keep the two patches separate to ease bisecting - I am going to repost the patches on top of scsi tree. Cheers! -- Regards, Alexander Gordeev agordeev@...hat.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists