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: Wed, 11 Jun 2014 10:24:55 +0200 [thread overview]
Message-ID: <xa1t38fb3lbc.fsf@mina86.com> (raw)
In-Reply-To: <20140610024910.GB19036@js1304-P5Q-DELUXE>
On Tue, Jun 10 2014, Joonsoo Kim <iamjoonsoo.kim@lge•com> wrote:
> Without including device.h, build failure occurs.
> In dma-contiguous.h, we try to access to dev->cma_area, so we need
> device.h. In the past, we included it luckily by swap.h in
> drivers/base/dma-contiguous.c. Swap.h includes node.h and then node.h
> includes device.h, so we were happy. But, in this patch, I remove
> 'include <linux/swap.h>' so we need to include device.h explicitly.
Ack.
--
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-11 8:24 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
2014-06-10 2:49 ` Joonsoo Kim
2014-06-11 8:24 ` Michal Nazarewicz [this message]
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=xa1t38fb3lbc.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