From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: "Hebbar, Shivananda" <x0hebbar@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC][PATCH v1 9/19] DSPBRIDGE: Cleanup custom error code (DSP_EFOPEN ->- EBADF)
Date: Wed, 21 Apr 2010 14:50:49 -0500 [thread overview]
Message-ID: <4BCF5719.70500@ti.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E7394044DEBEE0F@dbde02.ent.ti.com>
On 3/26/2010 9:28 PM, Hebbar, Shivananda wrote:
> From 3bf9c85d6d0794e790491334dca1dde8d0ada863 Mon Sep 17 00:00:00 2001
> From: Shivananda Hebbar<x0hebbar@ti.com>
> Date: Tue, 23 Mar 2010 13:24:31 -0600
> Subject: [PATCH] DSPBRIDGE: Cleanup custom error code (DSP_EFOPEN ->- EBADF)
>
> This patch replaces DSP_EFOPEN with -EBADF
>
> Signed-off-by: Shivananda Hebbar<x0hebbar@ti.com>
Rebased and pushed the entire series (1st set of 19 + 2nd set of 13),
fixed some wrong patch subjects among other issues.
It seems there is one thing left though, let me know if you will take
care of it.
TODO: print the status codes as decimal instead of hex.
- omar
prev parent reply other threads:[~2010-04-21 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 2:28 [RFC][PATCH v1 9/19] DSPBRIDGE: Cleanup custom error code (DSP_EFOPEN ->- EBADF) Hebbar, Shivananda
2010-04-21 19:50 ` 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=4BCF5719.70500@ti.com \
--to=omar.ramirez@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=x0hebbar@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