From: Michal Nazarewicz <mina86@mina86.com>
To: Feng Tang <feng.tang@intel.com>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"m.szyprowski\@samsung.com" <m.szyprowski@samsung.com>,
"kyungmin.park\@samsung.com" <kyungmin.park@samsung.com>,
"akpm\@linux-foundation.org" <akpm@linux-foundation.org>,
"iamjoonsoo.kim\@lge.com" <iamjoonsoo.kim@lge.com>,
"john.stultz\@linaro.org" <john.stultz@linaro.org>
Subject: Re: [PATCH] CMA: Don't return a valid cma for non-cma dev
Date: Wed, 05 Aug 2015 12:28:03 +0200 [thread overview]
Message-ID: <xa1tlhdqc9n0.fsf@mina86.com> (raw)
In-Reply-To: <20150805091917.GA27241@shbuild888>
On Wed, Aug 05 2015, Feng Tang wrote:
> that for a system which needs multiple cma heaps (like for security
> reason), they may have to share one struct device *dev, as in
> ion_cma_heap_create()
If you need several CMA areas to allocate from, create multiple struct
devices.
--
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:[~2015-08-05 10:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 2:37 [PATCH] CMA: Don't return a valid cma for non-cma dev Feng Tang
2015-07-30 13:59 ` Michal Nazarewicz
2015-07-31 2:51 ` Tang, Feng
2015-07-31 12:05 ` Michal Nazarewicz
2015-07-31 15:18 ` Feng Tang
2015-07-31 17:46 ` Michal Nazarewicz
2015-08-05 9:19 ` Feng Tang
2015-08-05 10:28 ` Michal Nazarewicz [this message]
2015-08-05 10:46 ` Feng Tang
2015-08-05 10:55 ` Feng Tang
2015-08-05 11:15 ` Michal Nazarewicz
2015-08-05 13:22 ` Feng Tang
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=xa1tlhdqc9n0.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@intel.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=john.stultz@linaro.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.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