From: dhobsong@igel.co.jp (Damian Hobson-Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] dma-mapping: Define dma_{alloc,free}_attrs() for all archs
Date: Fri, 24 May 2013 11:52:22 +0900 [thread overview]
Message-ID: <519ED5E6.7040506@igel.co.jp> (raw)
In-Reply-To: <20130523094709.GB16722@arm.com>
On 2013/05/23 18:47, Catalin Marinas wrote:
> On Thu, May 23, 2013 at 03:47:13AM +0100, Damian Hobson-Garcia wrote:
>> Hi Catalin,
>> On 2013/05/22 18:47, Catalin Marinas wrote:
>>> On Wed, May 22, 2013 at 03:37:17AM +0100, Damian Hobson-Garcia wrote:
>>>> Hello,
>>>> On 2013/04/30 12:01, Damian Hobson-Garcia wrote:
>>>>> Most architectures that define CONFIG_HAVE_DMA=y, have implementations for
>>>>> both dma_alloc_attrs() and dma_free_attrs(). All achitectures that do
>>>>> not define CONFIG_HAVE_DMA also have both of these definitions provided by
>>>>> dma-mapping-broken.h.
>>>
>>> BTW, shouldn't this be called CONFIG_HAVE_DMA_ATTRS?
>>
>> CONFIG_HAVE_DMA_ATTRS is currently used to enable the functions to
>> set/get the DMA attribute values. Poking through the headers, it looks
>> like the struct dma_attrs is defined regardless of the
>> CONFIG_HAVE_DMA_ATTRS setting, so in that respect
>> we always seem to "have" DMA attributes (if we have DMA), but they may
>> not always be meaningful (ie. set to some value).
>
> My point was about the commit log - grep'ing the kernel for
> CONFIG_HAVE_DMA did not return anything.
>
Oh yes, my mistake. It should be CONFIG_HAS_DMA instead of
CONFIG_HAVE_DMA. I'll update it.
Damian
--
Damian Hobson-Garcia
IGEL Co.,Ltd
http://www.igel.co.jp
next prev parent reply other threads:[~2013-05-24 2:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 3:01 [PATCH v2 0/4] dma-mapping: Define dma_{alloc, free}_attrs() for all archs Damian Hobson-Garcia
2013-05-22 2:37 ` [PATCH v2 0/4] dma-mapping: Define dma_{alloc,free}_attrs() " Damian Hobson-Garcia
2013-05-22 9:47 ` Catalin Marinas
2013-05-23 2:47 ` Damian Hobson-Garcia
2013-05-23 9:47 ` Catalin Marinas
2013-05-24 2:52 ` Damian Hobson-Garcia [this message]
2013-05-22 18:19 ` Helge Deller
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=519ED5E6.7040506@igel.co.jp \
--to=dhobsong@igel.co.jp \
--cc=linux-arm-kernel@lists.infradead.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: 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;
as well as URLs for NNTP newsgroup(s).