From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linaro-mm-sig@lists.linaro.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
iommu@lists.linux-foundation.org
Cc: 'Kyungmin Park' <kyungmin.park@samsung.com>,
'Arnd Bergmann' <arnd@arndb.de>, 'Joerg Roedel' <joro@8bytes.org>,
'Russell King - ARM Linux' <linux@arm.linux.org.uk>,
'Shariq Hasnain' <shariq.hasnain@linaro.org>,
'Chunsang Jeong' <chunsang.jeong@linaro.org>,
'Krishna Reddy' <vdumpa@nvidia.com>,
'KyongHo Cho' <pullip.cho@samsung.com>,
Andrzej Pietrasiewicz <andrzej.p@samsung.com>,
'Benjamin Herrenschmidt' <benh@kernel.crashing.org>,
'Kukjin Kim' <kgene.kim@samsung.com>'KyongHo Cho'
<pullip.cho@samsung.com>
Subject: RE: [PATCH 0/8 v4] ARM: DMA-mapping framework redesign
Date: Tue, 10 Jan 2012 09:42:37 +0100 [thread overview]
Message-ID: <012601cccf73$ce09a8f0$6a1cfad0$%szyprowski@samsung.com> (raw)
In-Reply-To: <1323448798-18184-1-git-send-email-m.szyprowski@samsung.com>
Hello,
To help everyone in testing and adapting our patches for his hardware
platform I've rebased our patches onto the latest v3.2 Linux kernel and
prepared a few GIT branches in our public repository. These branches
contain our memory management related patches posted in the following
threads:
"[PATCHv18 0/11] Contiguous Memory Allocator":
http://www.spinics.net/lists/linux-mm/msg28125.html
later called CMAv18,
"[PATCH 00/14] DMA-mapping framework redesign preparation":
http://www.spinics.net/lists/linux-sh/msg09777.html
and
"[PATCH 0/8 v4] ARM: DMA-mapping framework redesign":
http://www.spinics.net/lists/arm-kernel/msg151147.html
with the following update:
http://www.spinics.net/lists/arm-kernel/msg154889.html
later called DMAv5.
These branches are available in our public GIT repository:
git://git.infradead.org/users/kmpark/linux-samsung
http://git.infradead.org/users/kmpark/linux-samsung/
The following branches are available:
1) 3.2-cma-v18
Vanilla Linux v3.2 with fixed CMA v18 patches (first patch replaced
with the one from v17 to fix SMP issues, see the respective thread).
2) 3.2-dma-v5
Vanilla Linux v3.2 + iommu/next (IOMMU maintainer's patches) branch
with DMA-preparation and DMA-mapping framework redesign patches.
3) 3.2-cma-v18-dma-v5
Previous two branches merged together (DMA-mapping on top of CMA)
4) 3.2-cma-v18-dma-v5-exynos
Previous branch rebased on top of iommu/next + kgene/for-next (Samsung
SoC platform maintainer's patches) with new Exynos4 IOMMU driver by
KyongHo Cho and relevant glue code.
5) 3.2-dma-v5-exynos
Branch from point 2 rebased on top of iommu/next + kgene/for-next
(Samsung SoC maintainer's patches) with new Exynos4 IOMMU driver by
KyongHo Cho and relevant glue code.
I hope everyone will find a branch that suits his needs. :)
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
prev parent reply other threads:[~2012-01-10 8:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 16:39 [PATCH 0/8 v4] ARM: DMA-mapping framework redesign Marek Szyprowski
2011-12-09 16:39 ` Marek Szyprowski
2011-12-09 16:39 ` [PATCH 1/8] ARM: dma-mapping: remove offset parameter to prepare for generic dma_ops Marek Szyprowski
2011-12-09 16:39 ` Marek Szyprowski
2011-12-09 16:39 ` [PATCH 2/8] ARM: dma-mapping: use asm-generic/dma-mapping-common.h Marek Szyprowski
2011-12-09 16:39 ` Marek Szyprowski
2011-12-09 16:39 ` [PATCH 3/8] ARM: dma-mapping: implement dma sg methods on top of any generic dma ops Marek Szyprowski
2011-12-09 16:39 ` Marek Szyprowski
2011-12-09 16:39 ` [PATCH 4/8] ARM: dma-mapping: move all dma bounce code to separate dma ops structure Marek Szyprowski
2011-12-09 16:39 ` Marek Szyprowski
2011-12-09 16:39 ` [PATCH 5/8] ARM: dma-mapping: remove redundant code and cleanup Marek Szyprowski
2011-12-09 16:39 ` Marek Szyprowski
2011-12-09 16:39 ` [PATCH 6/8] common: dma-mapping: change alloc/free_coherent method to more generic alloc/free_attrs Marek Szyprowski
2011-12-09 16:39 ` Marek Szyprowski
2011-12-11 22:45 ` Stephen Rothwell
2011-12-11 22:45 ` Stephen Rothwell
2011-12-14 12:37 ` Marek Szyprowski
2011-12-09 16:39 ` [PATCH 7/8] ARM: dma-mapping: use alloc, mmap, free from dma_ops Marek Szyprowski
2011-12-09 16:39 ` [PATCH 8/8] ARM: dma-mapping: add support for IOMMU mapper Marek Szyprowski
2011-12-09 16:39 ` Marek Szyprowski
2012-01-09 15:49 ` [PATCH 8/8 RESEND] " Marek Szyprowski
2012-01-09 15:49 ` Marek Szyprowski
2012-01-25 12:59 ` Russell King - ARM Linux
2012-01-25 12:59 ` Russell King - ARM Linux
2012-01-26 8:09 ` Marek Szyprowski
2012-01-25 12:47 ` [PATCH 8/8] " Hiroshi Doyu
2012-01-25 12:47 ` Hiroshi Doyu
2012-01-26 7:46 ` Marek Szyprowski
2012-01-26 7:46 ` Marek Szyprowski
2012-01-10 8:42 ` Marek Szyprowski [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='012601cccf73$ce09a8f0$6a1cfad0$%szyprowski@samsung.com' \
--to=m.szyprowski@samsung.com \
--cc=andrzej.p@samsung.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=chunsang.jeong@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pullip.cho@samsung.com \
--cc=shariq.hasnain@linaro.org \
--cc=vdumpa@nvidia.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).