From: Maxime Bizon <mbizon@freebox.fr>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
lauraa@codeaurora.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org, mina86@mina86.com,
linux-mm@kvack.org, aneesh.kumar@linux.vnet.ibm.com,
Gregory Fong <gregory.0xf0@gmail.com>,
gioh.kim@lge.com, akpm@linux-foundation.org,
Brian Norris <computersforpeace@gmail.com>,
linux-arm-kernel@lists.infradead.org, m.szyprowski@samsung.com
Subject: Re: DMA allocations from CMA and fatal_signal_pending check
Date: Fri, 31 Oct 2014 22:07:10 +0100 [thread overview]
Message-ID: <1414789630.14835.49.camel@sakura.staff.proxad.net> (raw)
In-Reply-To: <20141031082818.GB14642@js1304-P5Q-DELUXE>
On Fri, 2014-10-31 at 17:28 +0900, Joonsoo Kim wrote:
> I guess that it is okay that bcm_sysport_open() return -EINTR?
actually, since CMA alloc is hidden behind dma_alloc_coherent(), all you
get back is NULL and then return ENOMEM.
--
Maxime
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-10-31 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 19:08 DMA allocations from CMA and fatal_signal_pending check Florian Fainelli
2014-10-31 8:28 ` Joonsoo Kim
2014-10-31 20:58 ` Florian Fainelli
2014-11-03 16:45 ` Michal Nazarewicz
2014-11-03 18:51 ` Florian Fainelli
2014-10-31 21:07 ` Maxime Bizon [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=1414789630.14835.49.camel@sakura.staff.proxad.net \
--to=mbizon@freebox.fr \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=computersforpeace@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gioh.kim@lge.com \
--cc=gregory.0xf0@gmail.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=lauraa@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mina86@mina86.com \
--cc=netdev@vger.kernel.org \
/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).