From: mina86@mina86•com (Michal Nazarewicz)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC PATCH 2/3] DMA, CMA: use general CMA reserved area management framework
Date: Tue, 03 Jun 2014 09:00:48 +0200 [thread overview]
Message-ID: <xa1twqcyjx3z.fsf@mina86.com> (raw)
In-Reply-To: <1401757919-30018-3-git-send-email-iamjoonsoo.kim@lge.com>
On Tue, Jun 03 2014, Joonsoo Kim wrote:
> Now, we have general CMA reserved area management framework,
> so use it for future maintainabilty. There is no functional change.
>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge•com>
Acked-by: Michal Nazarewicz <mina86@mina86•com>
> diff --git a/include/linux/dma-contiguous.h b/include/linux/dma-contiguous.h
> index dfb1dc9..ecb85ac 100644
> --- a/include/linux/dma-contiguous.h
> +++ b/include/linux/dma-contiguous.h
> @@ -53,9 +53,10 @@
>
> #ifdef __KERNEL__
>
> +#include <linux/device.h>
> +
Why is this suddenly required?
> struct cma;
> struct page;
> -struct device;
>
> #ifdef CONFIG_DMA_CMA
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Micha? ?mina86? Nazarewicz (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber•org>--ooO--(_)--Ooo--
next prev parent reply other threads:[~2014-06-03 7:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 1:11 [RFC PATCH 0/3] CMA: generalize CMA reserved area management code Joonsoo Kim
2014-06-03 1:11 ` [RFC PATCH 1/3] CMA: generalize CMA reserved area management functionality Joonsoo Kim
2014-06-03 6:56 ` Michal Nazarewicz
2014-06-10 2:41 ` Joonsoo Kim
2014-06-05 17:39 ` Aneesh Kumar K.V
2014-06-10 3:01 ` Joonsoo Kim
2014-06-03 1:11 ` [RFC PATCH 2/3] DMA, CMA: use general CMA reserved area management framework Joonsoo Kim
2014-06-03 7:00 ` Michal Nazarewicz [this message]
2014-06-10 2:49 ` Joonsoo Kim
2014-06-11 8:24 ` Michal Nazarewicz
2014-06-03 1:11 ` [RFC PATCH 3/3] PPC, KVM, " Joonsoo Kim
2014-06-03 7:02 ` Michal Nazarewicz
2014-06-03 9:20 ` Paolo Bonzini
2014-06-05 17:00 ` Aneesh Kumar K.V
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=xa1twqcyjx3z.fsf@mina86.com \
--to=mina86@mina86$(echo .)com \
--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