| 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: Tue, 8 Sep 2015 02:54:47 -0700 From: "Luis R. Rodriguez" <mcgrof@...not-panic.com> To: Arnd Bergmann <arnd@...db.de> Cc: "Luis R. Rodriguez" <mcgrof@...not-panic.com>, linux-arch@...r.kernel.org, Ingo Molnar <mingo@...nel.org>, schwidefsky@...ibm.com, heiko.carstens@...ibm.com, linux-s390@...r.kernel.org, Borislav Petkov <bp@...e.de>, Guenter Roeck <linux@...ck-us.net>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, Steven Rostedt <rostedt@...dmis.org> Subject: Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit On Wed, Sep 2, 2015 at 6:47 PM, Luis R. Rodriguez <mcgrof@...not-panic.com> wrote: > On Wed, Sep 2, 2015 at 6:44 PM, Luis R. Rodriguez <mcgrof@...e.com> wrote: >>> I don't think we really need to spell it out here. s390 PCI is different >>> from everybody else's in a lot of ways, so a simple 'depends on PCI && >>> !S390' for CONFIG_PCI_IOMAP seems simpler and more intuitive. >> >> Sure that would work as well. > > But on second thought it still would leave us reactive to S390, this > solution would get folks extending this asm-generic stuff to also have > something in place for S390, even if its just returning NULL. Arnd, thoughts? Luis -- 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