From: Vinod Koul <vinod.koul@intel.com>
To: alsa-devel@alsa-project.org
Cc: Vinod Koul <vinod.koul@intel.com>, Eric Laurent <elaurent@google.com>
Subject: [PATCH] fix error returned by compress_wait()
Date: Wed, 24 Jul 2013 23:26:17 +0530 [thread overview]
Message-ID: <1374688577-27976-1-git-send-email-vinod.koul@intel.com> (raw)
From: Eric Laurent <elaurent@google.com>
oops() expects positive error codes.
Signed-off-by: Eric Laurent <elaurent@google.com>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
---
compress.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/compress.c b/compress.c
index 734fbbf..0e71c28 100644
--- a/compress.c
+++ b/compress.c
@@ -623,7 +623,7 @@ int compress_wait(struct compress *compress, int timeout_ms)
return 0;
}
if (fds.revents & POLLERR) {
- return oops(compress, -EIO, "poll returned error!");
+ return oops(compress, EIO, "poll returned error!");
}
return ret;
}
--
1.7.0.4
reply other threads:[~2013-07-24 18:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1374688577-27976-1-git-send-email-vinod.koul@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=elaurent@google.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;
as well as URLs for NNTP newsgroup(s).