From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: linux-omap <linux-omap@vger.kernel.org>
Cc: Omar Ramirez Luna <omar.ramirez@ti.com>,
Nishanth Menon <nm@ti.com>, Hiroshi Doyu <Hiroshi.DOYU@nokia.com>,
Ameya Palande <ameya.palande@nokia.com>,
Fernando Guzman Lugo <x0095840@ti.com>
Subject: [PATCH 0/3] Interface tightening patches
Date: Wed, 13 Jan 2010 19:11:13 -0600 [thread overview]
Message-ID: <1263431476-19206-1-git-send-email-omar.ramirez@ti.com> (raw)
Set of patches containing ioctl interface checks, null pointers
checks and imporvement on resource handling on error.
Ernesto Ramos (3):
DSPBRIDGE: Interface tightening to check for invalid input
parameters
DSPBRIDGE: Undo allocation of resources in case of cp_to_usr fails
DSPBRIDGE: NULL Pointer Dereference fix
arch/arm/plat-omap/include/dspbridge/dbdefs.h | 4 +-
drivers/dsp/bridge/pmgr/wcd.c | 126 ++++++++++++++++++++-----
drivers/dsp/bridge/rmgr/nldr.c | 3 +-
drivers/dsp/bridge/rmgr/node.c | 6 +-
drivers/dsp/bridge/rmgr/proc.c | 9 +-
drivers/dsp/bridge/services/mem.c | 4 -
drivers/dsp/bridge/wmd/chnl_sm.c | 2 +-
7 files changed, 113 insertions(+), 41 deletions(-)
CC: Nishanth Menon <nm@ti.com>
CC: Hiroshi Doyu <Hiroshi.DOYU@nokia.com>
CC: Ameya Palande <ameya.palande@nokia.com>
CC: Fernando Guzman Lugo <x0095840@ti.com>
next reply other threads:[~2010-01-14 1:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 1:11 Omar Ramirez Luna [this message]
2010-01-14 1:11 ` [PATCH 1/3] DSPBRIDGE: Interface tightening to check for invalid input parameters Omar Ramirez Luna
2010-01-14 1:11 ` [PATCH 2/3] DSPBRIDGE: Undo allocation of resources in case of cp_to_usr fails Omar Ramirez Luna
2010-01-14 1:11 ` [PATCH 3/3] DSPBRIDGE: NULL Pointer Dereference fix Omar Ramirez Luna
2010-01-18 18:31 ` Ramirez Luna, Omar
2010-01-18 18:30 ` [PATCH 2/3] DSPBRIDGE: Undo allocation of resources in case of cp_to_usr fails Ramirez Luna, Omar
2010-01-18 18:30 ` [PATCH 1/3] DSPBRIDGE: Interface tightening to check for invalid input parameters Ramirez Luna, Omar
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=1263431476-19206-1-git-send-email-omar.ramirez@ti.com \
--to=omar.ramirez@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox