From: deller@gmx.de (Helge Deller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] dma-mapping: Define dma_{alloc,free}_attrs() for all archs
Date: Wed, 22 May 2013 20:19:37 +0200 [thread overview]
Message-ID: <519D0C39.6090201@gmx.de> (raw)
In-Reply-To: <519C2F5D.8000809@igel.co.jp>
On 05/22/2013 04:37 AM, 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.
>>
>> Provide a default definition for the archs that define CONFIG_HAVE_DMA=y,
>> but have no implementation for dma_{alloc,free}_attrs().
>>
>> As I don't have hardware for any of these systems, the patches are only
>> compile-tested where I could (arm64, s390) and untested for the archs
>> where I couldn't find a readily available prebuilt cross-compiler (c6x, parisc).
>>
>
>
>> arch/arm64/include/asm/dma-mapping.h | 17 +++++++++++------
>> arch/c6x/include/asm/dma-mapping.h | 3 +++
>> arch/parisc/include/asm/dma-mapping.h | 3 +++
>> arch/s390/include/asm/dma-mapping.h | 17 +++++++++++------
>> 4 files changed, 28 insertions(+), 12 deletions(-)
>>
>
> Since this series spans several architectures, what would be the best
> way to have this patch series merged?
> Should I resubmit each patch to the mailing list for each architecture
> separately?
I already pushed the parisc change upstream.
See commit 7f64fb41aad9a8504dd76e81b2391eae64e1498a
Helge
prev parent reply other threads:[~2013-05-22 18:19 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
2013-05-22 18:19 ` Helge Deller [this message]
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=519D0C39.6090201@gmx.de \
--to=deller@gmx.de \
--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).