From: Seth Forshee <seth.forshee@gmail.com>
To: Ameya Palande <ameya.palande@nokia.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH] DSPBRIDGE: Fix error handling in NODE_GetUUIDProps
Date: Mon, 23 Mar 2009 09:53:53 -0500 [thread overview]
Message-ID: <20090323145353.GD27379@linux-desktop> (raw)
In-Reply-To: <20090323143847.GC27379@linux-desktop>
On Mon, Mar 23, 2009 at 09:38:47AM -0500, Seth Forshee wrote:
> On Mon, Mar 23, 2009 at 03:15:07PM +0200, Ameya Palande wrote:
> > From: Seth Forshee <seth.forshee@gmail.com>
> >
> > The error handling is ineffective and can lead to an oops.
> >
> > Acked-by: Ameya Palande <ameya.palande@nokia.com>
> > Signed-off-by: Seth Forshee <seth.forshee@gmail.com>
>
> Ah, hadn't seen this one yet when I sent my previous reply. Thanks.
Whoops, there was a discussion on this topic on the omap-android list,
and I didn't notice that this patch was posted to the linux-omap list
instead of that one. Sorry for the noise.
Cheers,
Seth
prev parent reply other threads:[~2009-03-23 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 13:15 [PATCH] DSPBRIDGE: Fix error handling in NODE_GetUUIDProps Ameya Palande
2009-03-23 14:38 ` Seth Forshee
2009-03-23 14:53 ` Seth Forshee [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=20090323145353.GD27379@linux-desktop \
--to=seth.forshee@gmail.com \
--cc=ameya.palande@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox