From: Artem Bityutskiy <dedekind1@gmail.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: Sun, 11 Apr 2010 18:00:11 +0300 [thread overview]
Message-ID: <1270998011.2532.3.camel@localhost.localdomain> (raw)
In-Reply-To: <818EF96F5A7CC84789DD014773DB09548F6481CB@dlee01.ent.ti.com>
On Thu, 2010-04-08 at 18:43 -0500, 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)
Hi, I guess you noticed by now that you should not assume kzalloc
returns "paged" memory?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-11 15:00 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 [this message]
2010-04-28 1:06 ` Omar Ramirez Luna
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=1270998011.2532.3.camel@localhost.localdomain \
--to=dedekind1@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.