From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, James.Bottomley@SteelEye.com,
Tejun Heo <htejun@gmail.com>, Jeff Garzik <jeff@garzik.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH] dma-mapping-broken.h: flesh-out DMA API stubs
Date: Fri, 23 Feb 2007 04:42:43 +0100 [thread overview]
Message-ID: <20070223034243.GA7988@osiris.ibm.com> (raw)
In-Reply-To: <20070223005945.GA13084@tuxdriver.com>
On Thu, Feb 22, 2007 at 07:59:45PM -0500, John W. Linville wrote:
> This allows some drivers compile on arches that don't support DMA
> (e.g. s390).
Which drivers are we talking about? Last time I checked an allmodconfig
just compiled.
I'd rather like to the opposite: rip out everything that depends on DMA
(via e.g. CONFIG_HAS_DMA), so we don't have to compile in all the unused
code. If that is is possible...
--
Heiko Carstens
Linux on System z Development
IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Johann Weihen
Geschaeftsfuehrung : Herbert Kircher
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2007-02-23 3:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 0:59 [PATCH] dma-mapping-broken.h: flesh-out DMA API stubs John W. Linville
2007-02-23 3:42 ` Heiko Carstens [this message]
2007-02-23 6:13 ` Heiko Carstens
2007-02-23 9:50 ` Heiko Carstens
2007-02-23 13:57 ` Kyle McMartin
2007-02-23 14:39 ` John W. Linville
2007-02-26 13:57 ` [patch] Introduce CONFIG_HAS_DMA Heiko Carstens
2007-05-25 16:36 ` Dan Williams
2007-05-30 9:10 ` Cornelia Huck
2007-05-30 21:40 ` Williams, Dan J
2007-05-30 22:29 ` [PATCH] dma-mapping: prevent dma dependent code from linking on !HAS_DMA archs Dan Williams
2007-05-31 6:53 ` [patch] Introduce CONFIG_HAS_DMA Cornelia Huck
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=20070223034243.GA7988@osiris.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=schwidefsky@de.ibm.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.