Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1220667
| From | "Luis R. Rodriguez" <mcgrof@do-not-panic.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit |
| Date | 2015-09-08 12:00 +0200 |
| Message-ID | <q6nR1-Fh-29@gated-at.bofh.it> (permalink) |
| References | <q2C2d-2c4-3@gated-at.bofh.it> <q3gCn-1FJ-21@gated-at.bofh.it> <q4rP3-5Ru-5@gated-at.bofh.it> <q4rP4-5Ru-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Sep 2, 2015 at 6:47 PM, Luis R. Rodriguez <mcgrof@do-not-panic.com> wrote: > On Wed, Sep 2, 2015 at 6:44 PM, Luis R. Rodriguez <mcgrof@suse.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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit "Luis R. Rodriguez" <mcgrof@do-not-panic.com> - 2015-09-08 12:00 +0200
csiph-web