From: David Rientjes <rientjes@google.com>
To: "Sean O. Stalley" <sean.stalley@intel.com>
Cc: corbet@lwn.net, vinod.koul@intel.com, bhelgaas@google.com,
Julia.Lawall@lip6.fr, Gilles.Muller@lip6.fr,
nicolas.palix@imag.fr, mmarek@suse.cz, akpm@linux-foundation.org,
bigeasy@linutronix.de, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
linux-pci@vger.kernel.org, linux-mm@kvack.org,
cocci@systeme.lip6.fr
Subject: Re: [PATCH v2 1/4] mm: Add support for __GFP_ZERO flag to dma_pool_alloc()
Date: Wed, 12 Aug 2015 16:52:12 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1508121649310.30617@chino.kir.corp.google.com> (raw)
In-Reply-To: <1438371404-3219-2-git-send-email-sean.stalley@intel.com>
On Fri, 31 Jul 2015, Sean O. Stalley wrote:
> Currently the __GFP_ZERO flag is ignored by dma_pool_alloc().
> Make dma_pool_alloc() zero the memory if this flag is set.
>
> Signed-off-by: Sean O. Stalley <sean.stalley@intel.com>
Acked-by: David Rientjes <rientjes@google.com>
This has impacted us as well, and I'm glad to see it fixed.
--
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>
next prev parent reply other threads:[~2015-08-12 23:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 19:36 [PATCH v2 0/4] mm: add dma_pool_zalloc() & pci_pool_zalloc() Sean O. Stalley
2015-07-31 19:36 ` [PATCH v2 1/4] mm: Add support for __GFP_ZERO flag to dma_pool_alloc() Sean O. Stalley
2015-08-12 23:52 ` David Rientjes [this message]
2015-07-31 19:36 ` [PATCH v2 2/4] mm: Add dma_pool_zalloc() call to DMA API Sean O. Stalley
2015-07-31 19:36 ` [PATCH v2 3/4] pci: mm: Add pci_pool_zalloc() call Sean O. Stalley
2015-07-31 19:36 ` [PATCH v2 4/4] coccinelle: mm: scripts/coccinelle/api/alloc/pool_zalloc-simple.cocci Sean O. Stalley
2015-08-02 19:30 ` Julia Lawall
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=alpine.DEB.2.10.1508121649310.30617@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=bigeasy@linutronix.de \
--cc=cocci@systeme.lip6.fr \
--cc=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=nicolas.palix@imag.fr \
--cc=sean.stalley@intel.com \
--cc=vinod.koul@intel.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