From: Joerg Roedel <joro@8bytes.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-mips@linux-mips.org, linux-ia64@vger.kernel.org,
a-jacquiot@ti.com, catalin.marinas@arm.com,
Ming Lei <ming.lei@canonical.com>,
shuahkhan@gmail.com, sparclinux@vger.kernel.org,
linux-c6x-dev@linux-c6x.org, linux-sh@vger.kernel.org,
msalter@redhat.com, shuah.khan@hp.com, fenghua.yu@intel.com,
microblaze-uclinux@itee.uq.edu.au,
linux-arm-kernel@lists.infradead.org, monstr@monstr.eu,
tony.luck@intel.com, LKML <linux-kernel@vger.kernel.org>,
ralf@linux-mips.org, lethal@linux-sh.org,
linuxppc-dev@lists.ozlabs.org, davem@davemloft.net
Subject: Re: [PATCH 0/9] dma_debug: add debug_dma_mapping_error support to architectures that support DMA_DEBUG_API
Date: Sun, 2 Dec 2012 15:06:45 +0100 [thread overview]
Message-ID: <20121202140644.GP30633@8bytes.org> (raw)
In-Reply-To: <50B34B0F.3080204@samsung.com>
Hi Marek,
On Mon, Nov 26, 2012 at 11:57:19AM +0100, Marek Szyprowski wrote:
> I've took all the patches to the next-dma-debug branch in my tree, I sorry
> that You have to wait so long for it. My branch is based on Joerg's
> dma-debug branch and I've included it for testing in linux-next branch.
The patches are now two times in next. One version from my tree and one
from yours. Please remove the version from your tree, the patches should
go upstream via my dma-debug branch.
Joerg
next prev parent reply other threads:[~2012-12-02 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 21:29 [PATCH 0/9] dma_debug: add debug_dma_mapping_error support to architectures that support DMA_DEBUG_API Shuah Khan
2012-11-26 10:57 ` Marek Szyprowski
2012-11-26 11:20 ` Joerg Roedel
2012-12-02 14:06 ` Joerg Roedel [this message]
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=20121202140644.GP30633@8bytes.org \
--to=joro@8bytes.org \
--cc=a-jacquiot@ti.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=fenghua.yu@intel.com \
--cc=lethal@linux-sh.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=ming.lei@canonical.com \
--cc=monstr@monstr.eu \
--cc=msalter@redhat.com \
--cc=ralf@linux-mips.org \
--cc=shuah.khan@hp.com \
--cc=shuahkhan@gmail.com \
--cc=sparclinux@vger.kernel.org \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).