From: Shuah Khan <shuah.khan@hp•com>
To: Joerg Roedel <joro@8bytes•org>,
a-jacquiot@ti•com, fenghua.yu@intel•com, catalin.marinas@arm•com,
lethal@linux-sh•org, benh@kernel•crashing.org,
ralf@linux-mips•org, tony.luck@intel•com, davem@davemloft•net,
m.szyprowski@samsung•com, msalter@redhat•com, monstr@monstr•eu,
Ming Lei <ming.lei@canonical•com>
Cc: linux-mips@linux-mips•org, linux-ia64@vger•kernel.org,
linux-c6x-dev@linux-c6x•org, linux-sh@vger•kernel.org,
microblaze-uclinux@itee•uq.edu.au,
LKML <linux-kernel@vger•kernel.org>,
shuahkhan@gmail•com, sparclinux@vger•kernel.org,
linuxppc-dev@lists•ozlabs.org,
linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/9] dma_debug: add debug_dma_mapping_error support to architectures that support DMA_DEBUG_API
Date: Fri, 23 Nov 2012 14:29:02 -0700 [thread overview]
Message-ID: <1353706142.5270.93.camel@lorien2> (raw)
An earlier patch added dma mapping error debug feature to dma_debug
infrastructure. References:
https://lkml.org/lkml/2012/10/8/296
https://lkml.org/lkml/2012/11/3/219
The following series of patches adds the call to debug_dma_mapping_error() to
architecture specific dma_mapping_error() interfaces on the following
architectures that support CONFIG_DMA_API_DEBUG.
arm64
c6x
ia64
microblaze
mips
powerpc
sh
sparc
tile
arm - Change is already in Marek's dma-mapping tree[1]
https://patchwork.kernel.org/patch/1625601/
microblaze - Change is already in linux-next. Including it for completeness
linux-next commit f229605441030bcd315c21d97b25889d63ed0130
x86 - done in the first patch that added the feature.
ARM64: dma_debug: add debug_dma_mapping_error support
c6x: dma_debug: add debug_dma_mapping_error support
ia64: dma_debug: add debug_dma_mapping_error support
microblaze: dma-mapping: support debug_dma_mapping_error
mips: dma_debug: add debug_dma_mapping_error support
powerpc: dma_debug: add debug_dma_mapping_error support
sh: dma_debug: add debug_dma_mapping_error support
sparc: dma_debug: add debug_dma_mapping_error support
tile: dma_debug: add debug_dma_mapping_error support
Thanks,
-- Shuah
next reply other threads:[~2012-11-23 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 21:29 Shuah Khan [this message]
2012-11-26 10:57 ` [PATCH 0/9] dma_debug: add debug_dma_mapping_error support to architectures that support DMA_DEBUG_API Marek Szyprowski
2012-11-26 11:20 ` Joerg Roedel
2012-12-02 14:06 ` Joerg Roedel
2012-12-03 8:51 ` Marek Szyprowski
2012-11-26 11:22 ` Joerg Roedel
2012-11-26 16:09 ` Shuah Khan
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=1353706142.5270.93.camel@lorien2 \
--to=shuah.khan@hp$(echo .)com \
--cc=a-jacquiot@ti$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=fenghua.yu@intel$(echo .)com \
--cc=joro@8bytes$(echo .)org \
--cc=lethal@linux-sh$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-c6x-dev@linux-c6x$(echo .)org \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mips@linux-mips$(echo .)org \
--cc=linux-sh@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=m.szyprowski@samsung$(echo .)com \
--cc=microblaze-uclinux@itee$(echo .)uq.edu.au \
--cc=ming.lei@canonical$(echo .)com \
--cc=monstr@monstr$(echo .)eu \
--cc=msalter@redhat$(echo .)com \
--cc=ralf@linux-mips$(echo .)org \
--cc=shuahkhan@gmail$(echo .)com \
--cc=sparclinux@vger$(echo .)kernel.org \
--cc=tony.luck@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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