From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, NeilBrown <neilb@suse.de>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: RE: 2.6.22-rc1-mm1 - s390 vs. md
Date: Wed, 23 May 2007 10:05:39 +0200 [thread overview]
Message-ID: <1179907539.17849.16.camel@localhost> (raw)
In-Reply-To: <0C7297FA1D2D244A9C7F6959C0BF1E5201E39968@azsmsx413.amr.corp.intel.com>
On Tue, 2007-05-22 at 17:25 -0700, Williams, Dan J wrote:
> The approach I have taken is to add the missing definitions to
> include/asm-s390/dma-mapping.h [ a non-outlook-mangled version of the
> patch is pushed out in my rebased git tree ]. I was not able to fully
> compile-test this change as the three s390-cross-toolchains I tried
> each
We are trying to get rid of dma-mapping.h, see the last change to the
file with commit 411f0f3edc141a582190d3605cadd1d993abb6df. I don't think
we should reintroduce dma related definition but split the async_tx in a
way that allows to compile it on an architecture with CONFIG_NO_DMA=y
(yes I know that is harder that to just add the dma stubs).
You've said that there is a software implementation if there is no dma
engine present. This software implementation should be independent of
dma-mapping.h. Without having looked at the code, isn't it possible to
isolate that software implementation into its own C file? That would be
the only one that gets compiled for s390.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2007-05-23 8:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 6:36 2.6.22-rc1-mm1 - s390 vs. md Williams, Dan J
2007-05-17 6:36 ` Williams, Dan J
2007-05-18 5:39 ` Cornelia Huck
2007-05-18 5:39 ` Cornelia Huck
2007-05-18 16:30 ` Williams, Dan J
2007-05-18 16:30 ` Williams, Dan J
2007-05-21 7:24 ` Cornelia Huck
2007-05-21 7:24 ` Cornelia Huck
2007-05-21 8:52 ` Williams, Dan J
2007-05-21 8:52 ` Williams, Dan J
2007-05-23 0:25 ` Williams, Dan J
2007-05-23 0:25 ` Williams, Dan J
2007-05-23 8:05 ` Martin Schwidefsky [this message]
2007-05-23 8:46 ` Cornelia Huck
2007-05-23 8:55 ` Martin Schwidefsky
2007-05-24 22:11 ` Williams, Dan J
2007-05-24 22:11 ` Williams, Dan J
2007-05-25 6:02 ` Cornelia Huck
2007-05-25 6:02 ` Cornelia Huck
-- strict thread matches above, loose matches on Subject: below --
2007-05-16 3:19 2.6.22-rc1-mm1 Andrew Morton
2007-05-16 7:57 ` 2.6.22-rc1-mm1 - s390 vs. md Cornelia Huck
2007-05-16 17:21 ` Williams, Dan J
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=1179907539.17849.16.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cornelia.huck@de.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=neilb@suse.de \
/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.