LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com> To: Heiko Carstens <heiko.carstens@de.ibm.com> Cc: Andrew Morton <akpm@linux-foundation.org>, Linus Torvalds <torvalds@linux-foundation.org>, Martin Schwidefsky <schwidefsky@de.ibm.com>, Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org Subject: Re: [PATCH] iomap: make PCI iomap stuff excluded when PCI isn't configured Date: Sat, 10 Feb 2007 17:14:13 -0500 [thread overview] Message-ID: <45CE43B5.2020806@gmail.com> (raw) In-Reply-To: <20070210194630.GA13416@osiris.ibm.com> Heiko Carstens wrote: > On Sat, Feb 10, 2007 at 12:43:16PM -0500, Tejun Heo wrote: \>> Heiko, how about this? Does it fix s390? > > Unfortunately not. Now I get > > CC lib/iomap.o > lib/iomap.c: In function 'devm_ioport_map_release': > lib/iomap.c:270: warning: implicit declaration of function 'ioport_unmap' > lib/iomap.c: In function 'devm_ioport_map': > lib/iomap.c:297: warning: implicit declaration of function 'ioport_map' > lib/iomap.c:297: warning: assignment makes pointer from integer without a cast I think an arch needs to support ioport_map/unmap and noncoherent dma (just alias to coherent interface on x86/amd64) interface whether PCI is implemented or not. No? -- tejun
next prev parent reply other threads:[~2007-02-10 22:14 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-10 11:43 [patch] More defines for dma-mapping-broken.h Heiko Carstens 2007-02-10 17:43 ` [PATCH] iomap: make PCI iomap stuff excluded when PCI isn't configured Tejun Heo 2007-02-10 19:46 ` Heiko Carstens 2007-02-10 22:14 ` Tejun Heo [this message] 2007-02-10 22:25 ` Linus Torvalds 2007-02-10 22:50 ` Al Viro 2007-02-10 23:55 ` Al Viro 2007-02-11 16:45 ` Martin Schwidefsky 2007-02-11 18:15 ` Al Viro 2007-02-11 0:15 ` Heiko Carstens 2007-02-11 5:20 ` Al Viro 2007-02-11 2:41 ` Randy Dunlap 2007-02-11 15:49 ` [patch] More defines for dma-mapping-broken.h Jeff Garzik
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=45CE43B5.2020806@gmail.com \ --to=htejun@gmail.com \ --cc=akpm@linux-foundation.org \ --cc=heiko.carstens@de.ibm.com \ --cc=jgarzik@pobox.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-s390@vger.kernel.org \ --cc=schwidefsky@de.ibm.com \ --cc=torvalds@linux-foundation.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).