From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH v3] sparc32: dma_alloc_coherent must honour gfp flags
Date: Thu, 11 Sep 2014 19:51:05 +0000 [thread overview]
Message-ID: <5411FD29.5050005@gaisler.com> (raw)
In-Reply-To: <1410351472-10501-1-git-send-email-daniel@gaisler.com>
On 09/10/2014 11:03 PM, David Miller wrote:
> From: Daniel Hellstrom<daniel@gaisler.com>
> Date: Wed, 10 Sep 2014 14:17:52 +0200
>
>> dma_zalloc_coherent() calls dma_alloc_coherent(__GFP_ZERO)
>> but the sparc32 implementations sbus_alloc_coherent() and
>> pci32_alloc_coherent() doesn't take the gfp flags into
>> account.
>>
>> Tested on the SPARC32/LEON GRETH Ethernet driver which fails
>> due to dma_alloc_coherent(__GFP_ZERO) returns non zeroed
>> pages.
>>
>> Signed-off-by: Daniel Hellstrom<daniel@gaisler.com>
> Applied, thanks Daniel.
Thanks! I think this is subject for the stable branches.
prev parent reply other threads:[~2014-09-11 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 12:17 [PATCH v3] sparc32: dma_alloc_coherent must honour gfp flags Daniel Hellstrom
2014-09-10 21:03 ` David Miller
2014-09-11 19:51 ` Daniel Hellstrom [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=5411FD29.5050005@gaisler.com \
--to=daniel@gaisler.com \
--cc=sparclinux@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).