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
| ||
|
Message-ID: <20140306214356.GA16376@dhcp-26-207.brq.redhat.com> Date: Thu, 6 Mar 2014 22:43:57 +0100 From: Alexander Gordeev <agordeev@...hat.com> To: Dan Williams <dan.j.williams@...el.com> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Vinod Koul <vinod.koul@...el.com>, "dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>, linux-pci@...r.kernel.org Subject: Re: [PATCH v2 RESEND 1/4] ioat: Use pci_enable_msix_exact() instead of pci_enable_msix() On Thu, Mar 06, 2014 at 01:09:39PM -0800, Dan Williams wrote: > Can you point me to the background for this change. From the > changelog I have no idea what this patch does or why I need to apply > it. Function pci_enable_msix() returns a tri-state value while pci_enable_msi_exact() is a canonical zero/-errno variant. The former is being phased out in favor of the latter. In case of 'ioat' there (should be) no difference. HTH. -- 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