public inbox for openrisc@lists.librecores.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 19:10:56 +0100	[thread overview]
Message-ID: <20181214181056.GA17941@ravnborg.org> (raw)
In-Reply-To: <20181214082515.14835-2-hch@lst.de>

Hi Christoph,

I stumbled upon this one:

#define __get_dma_pages(gfp_mask, order) \
                __get_free_pages((gfp_mask) | GFP_DMA, (order))

(include/linux/gfp.h)
Should it also have the __GFP_ZERO treatment?
Or maybe this is already done in your tree..

As for the sparc bits:
Acked-by: Sam Ravnborg <sam@ravnborg.org> [sparc]

	Sam

  parent reply	other threads:[~2018-12-14 18:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14  8:25 [OpenRISC] ensure dma_alloc_coherent always returns zeroed memory Christoph Hellwig
2018-12-14  8:25 ` [OpenRISC] [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_* Christoph Hellwig
2018-12-14  9:54   ` Geert Uytterhoeven
2018-12-14  9:55     ` Geert Uytterhoeven
2018-12-14 11:47     ` Christoph Hellwig
2018-12-14 12:36       ` Geert Uytterhoeven
2018-12-14 14:14       ` Greg Ungerer
2018-12-17 11:59         ` Christoph Hellwig
2018-12-14 12:12   ` Eugeniy Paltsev
2018-12-14 12:21     ` hch
2018-12-14 18:10   ` Sam Ravnborg [this message]
2018-12-14 18:35     ` Christoph Hellwig
2018-12-14  8:25 ` [OpenRISC] [PATCH 2/2] dma-mapping: deprecate dma_zalloc_coherent Christoph Hellwig
2018-12-14 13:33 ` [OpenRISC] ensure dma_alloc_coherent always returns zeroed memory Christoph Hellwig
2018-12-19 16:59 ` Christoph Hellwig
     [not found]   ` <1545316369.14089.20.camel@synopsys.com>
2018-12-20 14:34     ` hch
     [not found]       ` <1545316759.14089.22.camel@synopsys.com>
2018-12-20 14:46         ` hch
2018-12-20 17:37           ` hch

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=20181214181056.GA17941@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=openrisc@lists.librecores.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