From: lethal@linux-sh•org (Paul Mundt)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCHv2 3/4] mm: vmalloc: add VM_DMA flag to indicate areas used by dma-mapping framework
Date: Thu, 24 May 2012 21:28:54 +0900 [thread overview]
Message-ID: <20120524122854.GD11860@linux-sh.org> (raw)
In-Reply-To: <01e501cd39a8$67f34ea0$37d9ebe0$%szyprowski@samsung.com>
On Thu, May 24, 2012 at 02:26:12PM +0200, Marek Szyprowski wrote:
> On Tuesday, May 22, 2012 9:08 AM Minchan Kim wrote:
> > Hmm, VM_DMA would become generic flag?
> > AFAIU, maybe VM_DMA would be used only on ARM arch.
>
> Right now yes, it will be used only on ARM architecture, but maybe other architecture will
> start using it once it is available.
>
There's very little about the code in question that is ARM-specific to
begin with. I plan to adopt similar changes on SH once the work has
settled one way or the other, so we'll probably use the VMA flag there,
too.
next prev parent reply other threads:[~2012-05-24 12:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 10:54 [PATCHv2 0/4] ARM: replace custom consistent dma region with vmalloc Marek Szyprowski
2012-05-17 10:54 ` [PATCHv2 1/4] mm: vmalloc: use const void * for caller argument Marek Szyprowski
2012-05-22 6:58 ` Minchan Kim
2012-05-17 10:54 ` [PATCHv2 2/4] mm: vmalloc: export find_vm_area() function Marek Szyprowski
2012-05-22 7:01 ` Minchan Kim
2012-05-17 10:54 ` [PATCHv2 3/4] mm: vmalloc: add VM_DMA flag to indicate areas used by dma-mapping framework Marek Szyprowski
2012-05-22 7:07 ` Minchan Kim
2012-05-24 12:26 ` Marek Szyprowski
2012-05-24 12:28 ` Paul Mundt [this message]
2012-05-27 12:35 ` KOSAKI Motohiro
2012-05-28 8:19 ` Marek Szyprowski
2012-05-29 15:07 ` Konrad Rzeszutek Wilk
2012-05-17 10:54 ` [PATCHv2 4/4] ARM: dma-mapping: remove custom consistent dma region Marek Szyprowski
2012-05-22 7:33 ` Minchan Kim
2012-05-22 12:50 ` Marek Szyprowski
2012-05-30 0:11 ` KOSAKI Motohiro
2012-05-30 7:15 ` Marek Szyprowski
2012-05-30 7:22 ` KOSAKI Motohiro
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=20120524122854.GD11860@linux-sh.org \
--to=lethal@linux-sh$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/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