From: "Ramirez Luna, Omar" <omar.ramirez@ti.com>
To: "Guzman Lugo, Fernando" <fernando.lugo@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Cc: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
Ameya Palande <ameya.palande@nokia.com>,
"felipe.contreras@nokia.com" <felipe.contreras@nokia.com>
Subject: RE: [PATCH] DSPBRIDGE: Avoid possible NULL pointer dereference in dspbridge
Date: Fri, 11 Jun 2010 00:08:30 -0500 [thread overview]
Message-ID: <27F9C60D11D683428E133F85D2BB4A53043E7CD93C@dlee03.ent.ti.com> (raw)
In-Reply-To: <496565EC904933469F292DDA3F1663E602CB048971@dlee06.ent.ti.com>
>From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Guzman
>Lugo, Fernando
>Sent: Thursday, April 08, 2010 7:17 PM
>To: linux-omap@vger.kernel.org
>Cc: Hiroshi DOYU; Ameya Palande; felipe.contreras@nokia.com
>Subject: [PATCH] DSPBRIDGE: Avoid possible NULL pointer dereference in dspbridge
>
>From 1471823b7a143bbb9566aaa192880309668f1bf9 Mon Sep 17 00:00:00 2001
>From: Ernesto Ramos <ernesto@ti.com>
>Date: Wed, 24 Mar 2010 16:37:38 -0600
>Subject: [PATCH] DSPBRIDGE: Avoid possible NULL pointer dereference in dspbridge
>
>Avoid possible NULL pointer dereference in dspbridge reported by KW.
>
>Signed-off-by: Ernesto Ramos <ernesto@ti.com>
>---
> drivers/dsp/bridge/pmgr/dev.c | 14 +++-----
> drivers/dsp/bridge/rmgr/nldr.c | 20 +++++++-----
> drivers/dsp/bridge/rmgr/node.c | 8 ++++-
> drivers/dsp/bridge/rmgr/proc.c | 51 +++++++++++++++++++++----------
> drivers/dsp/bridge/wmd/io_sm.c | 8 ++++-
> drivers/dsp/bridge/wmd/tiomap3430.c | 2 +-
> drivers/dsp/bridge/wmd/tiomap3430_pwr.c | 4 ++-
> 7 files changed, 67 insertions(+), 40 deletions(-)
>
Pushed to dspbridge.
- Omar
prev parent reply other threads:[~2010-06-11 5:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 0:17 [PATCH] DSPBRIDGE: Avoid possible NULL pointer dereference in dspbridge Guzman Lugo, Fernando
2010-06-11 5:08 ` Ramirez Luna, Omar [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=27F9C60D11D683428E133F85D2BB4A53043E7CD93C@dlee03.ent.ti.com \
--to=omar.ramirez@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.contreras@nokia.com \
--cc=fernando.lugo@ti.com \
--cc=linux-omap@vger.kernel.org \
/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.