From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: "Guzman Lugo, Fernando" <x0095840@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Palande Ameya (Nokia-D/Helsinki)" <ameya.palande@nokia.com>,
"Doyu Hiroshi (Nokia-D/Helsinki)" <hiroshi.doyu@nokia.com>,
Felipe Contreras <felipe.contreras@nokia.com>
Subject: Re: [PATCH 0/3] DSPBRIDGE: simplify ntfy module
Date: Mon, 5 Apr 2010 21:49:12 -0500 [thread overview]
Message-ID: <4BBAA128.6070208@ti.com> (raw)
In-Reply-To: <496565EC904933469F292DDA3F1663E602CADC2FF1@dlee06.ent.ti.com>
On 3/24/2010 10:52 PM, Guzman Lugo, Fernando wrote:
> From 87f5751e8838fae3b3eed189eaa9a94a6d8e1ebd Mon Sep 17 00:00:00 2001
> From: Fernando Guzman Lugo<x0095840@ti.com>
> Date: Wed, 24 Mar 2010 21:53:02 -0600
> Subject: [PATCH] DSPBRIDGE: simplify ntfy module
>
> This set of patches simplifies the ntfy and also use kernel functions
> for notifications. Always keeping the same behavior that it had before
> the changes. That is the reason the code could no be simplified a little
> more.
>
> Fernando Guzman Lugo (3):
> DSPBRIDGE: remove ntfy_init/exit functions
> DSPBRIDGE: allocation of ntfy object take out of ntfy module.
> DSPBRIDGE: simplify and make more use of kernel function in notify
> module
>
> arch/arm/plat-omap/include/dspbridge/ntfy.h | 275 +++++++++++++++++---------
> drivers/dsp/bridge/rmgr/node.c | 22 ++-
> drivers/dsp/bridge/rmgr/proc.c | 16 ++-
> drivers/dsp/bridge/services/ntfy.c | 282 +--------------------------
> drivers/dsp/bridge/services/services.c | 6 +-
> drivers/dsp/bridge/wmd/chnl_sm.c | 19 ++-
> drivers/dsp/bridge/wmd/msg_sm.c | 23 ++-
> drivers/dsp/bridge/wmd/ue_deh.c | 19 ++-
> 8 files changed, 270 insertions(+), 392 deletions(-)
>
> --
Pushed to dspbridge.
- omar
prev parent reply other threads:[~2010-04-06 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 3:52 [PATCH 0/3] DSPBRIDGE: simplify ntfy module Guzman Lugo, Fernando
2010-04-06 2:49 ` Omar Ramirez Luna [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=4BBAA128.6070208@ti.com \
--to=omar.ramirez@ti.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.contreras@nokia.com \
--cc=hiroshi.doyu@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=x0095840@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.