From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: "Gomez Castellanos, Ivan" <ivan.gomez@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
Ameya Palande <ameya.palande@nokia.com>,
"Menon, Nishanth" <nm@ti.com>
Subject: Re: [PATCH 01/13] DSPBRIDGE: Replace mem_calloc() by kzalloc() or __vmalloc()
Date: Tue, 27 Apr 2010 20:06:12 -0500 [thread overview]
Message-ID: <4BD78A04.8020905@ti.com> (raw)
In-Reply-To: <818EF96F5A7CC84789DD014773DB09548F6481CB@dlee01.ent.ti.com>
On 4/8/2010 6:43 PM, Gomez Castellanos, Ivan wrote:
> From 0306e1ff7c9160dbc5eb9fffcd789a40bea0debb Mon Sep 17 00:00:00 2001
> From: Ivan Gomez Castellanos<ivan.gomez@ti.com>
> Date: Fri, 19 Mar 2010 16:43:26 -0600
> Subject: [PATCH 01/13] DSPBRIDGE: Replace mem_calloc() by kzalloc() or __vmalloc()
>
> This is needed because the file drivers/dsp/bridge/services/mem.c
> is going to be deleted. The changes should be as follows:
>
> mem_calloc(x, MEM_PAGED) ==> kzalloc(x, GFP_KERNEL)
> mem_calloc(x, MEM_NONPAGED) ==> kzalloc(x, GFP_KERNEL)
> mem_calloc(x, MEM_MEM_LARGEVIRTMEM) ==>
> __vmalloc(x, GFP_KERNEL | __GFP_HIGHMEM | __GFP_ZERO, PAGE_KERNEL);
>
> If running in atomic context, then the GFP_KERNEL argument
> is changed to GFP_ATOMIC.
>
> Signed-off-by: Ivan Gomez Castellanos<ivan.gomez@ti.com>
> ---
Rebased and pushed the entire series.
- omar
next prev parent reply other threads:[~2010-04-28 1:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 23:43 [PATCH 01/13] DSPBRIDGE: Replace mem_calloc() by kzalloc() or __vmalloc() Gomez Castellanos, Ivan
2010-04-11 15:00 ` Artem Bityutskiy
2010-04-28 1:06 ` Omar Ramirez Luna [this message]
2010-05-13 19:36 ` Felipe Contreras
2010-05-13 21:56 ` Gomez Castellanos, Ivan
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=4BD78A04.8020905@ti.com \
--to=omar.ramirez@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.contreras@gmail.com \
--cc=ivan.gomez@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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;
as well as URLs for NNTP newsgroup(s).