From: Arnd Bergmann <arnd@arndb.de>
To: tom.leiming@gmail.com
Cc: joerg.roedel@amd.com, fujita.tomonori@lab.ntt.co.jp,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 0/3] dma-mapping:remove CONFIG_HAVE_DMA_ATTRS
Date: Sun, 5 Jul 2009 13:19:36 +0200 [thread overview]
Message-ID: <200907051319.37169.arnd@arndb.de> (raw)
In-Reply-To: <1246674895-9610-1-git-send-email-tom.leiming@gmail.com>
On Saturday 04 July 2009, tom.leiming@gmail.com wrote:
> 2,Disabling CONFIG_HAVE_DMA_ATTRS may lead to a compile failure;
I'm not sure I understand this point. CONFIG_HAVE_DMA_ATTRS tells
the common code whether the architecture understands dma attributes.
If you enable it on all architectures, you will get new compile
failures on all those that don't understand them, while the current
code correctly falls back on the standard functions.
I think it makes sense to combine CONFIG_HAVE_DMA_ATTRS with the
use of dma-mapping-common.h, but the majority of the architectures
just uses a static mapping, where attributes make no sense.
You also missed powerpc64, which selects CONFIG_HAVE_DMA_ATTRS
but does not (yet) use dma-mapping-common.h.
Arnd <><
next prev parent reply other threads:[~2009-07-05 11:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-04 2:34 [PATCH 0/3] dma-mapping:remove CONFIG_HAVE_DMA_ATTRS tom.leiming
2009-07-04 2:34 ` [PATCH 1/3] " tom.leiming
2009-07-04 2:34 ` [PATCH 2/3] dma-mapping:X86:remove CONFIG_HAVE_DMA_ATTRS tom.leiming
2009-07-04 2:34 ` [PATCH 3/3] dma-mapping:IA64:remove CONFIG_HAVE_DMA_ATTRS tom.leiming
2009-07-05 11:19 ` Arnd Bergmann [this message]
2009-07-05 12:44 ` [PATCH 0/3] dma-mapping:remove CONFIG_HAVE_DMA_ATTRS Ming Lei
2009-07-05 13:37 ` Ming Lei
2009-07-05 19:17 ` Arnd Bergmann
2009-07-06 2:28 ` FUJITA Tomonori
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=200907051319.37169.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox