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: Wed, 8 Oct 2008 10:56:18 +0800 From: "Zhao, Yu" <yu.zhao@...el.com> To: Matthew Wilcox <matthew@....cx>, Jesse Barnes <jbarnes@...tuousgeek.org> CC: "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, Randy Dunlap <randy.dunlap@...cle.com>, Grant Grundler <grundler@...isc-linux.org>, Alex Chiang <achiang@...com>, Roland Dreier <rdreier@...co.com>, Greg KH <greg@...ah.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>, "virtualization@...ts.linux-foundation.org" <virtualization@...ts.linux-foundation.org> Subject: RE: [PATCH 3/6 v3] PCI: support ARI capability On Friday, October 03, 2008 12:17 AM, Matthew Wilcox wrote: >On Thu, Oct 02, 2008 at 09:03:15AM -0700, Jesse Barnes wrote: >> Maybe we should be consistent with the other APIs and call it pci_enable_ari >> (like we do for wake & msi). Looks pretty good otherwise. > >Those APIs are for drivers ... this is internal. I don't have any >objection of my own, though I agree with Alex's remark that the printk >is unnecessary and just adds clutter to the boot process. Will rename the function to pci_enable_ari, and remove the printk. Thanks. > >-- >Matthew Wilcox Intel Open Source Technology Centre >"Bill, look, we understand that you're interested in selling us this >operating system, but compare it to ours. We can't possibly take such >a retrograde step." >-- >To unsubscribe from this list: send the line "unsubscribe kvm" in >the body of a message to majordomo@...r.kernel.org >More majordomo info at http://vger.kernel.org/majordomo-info.html -- 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