From: Cyril Bur <cyrilbur@gmail.com>
To: linuxppc-dev@lists.ozlabs.org, linux-mtd@lists.infradead.org
Cc: dwmw2@infradead.org, stewart@linux.vnet.ibm.com
Subject: [PATCH 4/5] powerpc/powernv: Add OPAL_BUSY to opal_error_code()
Date: Thu, 29 Jun 2017 16:54:12 +1000 [thread overview]
Message-ID: <20170629065413.19845-5-cyrilbur@gmail.com> (raw)
In-Reply-To: <20170629065413.19845-1-cyrilbur@gmail.com>
Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
---
arch/powerpc/platforms/powernv/opal.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/platforms/powernv/opal.c b/arch/powerpc/platforms/powernv/opal.c
index 59684b4af4d1..f87e000e7c28 100644
--- a/arch/powerpc/platforms/powernv/opal.c
+++ b/arch/powerpc/platforms/powernv/opal.c
@@ -930,6 +930,7 @@ int opal_error_code(int rc)
case OPAL_PARAMETER: return -EINVAL;
case OPAL_ASYNC_COMPLETION: return -EINPROGRESS;
+ case OPAL_BUSY:
case OPAL_BUSY_EVENT: return -EBUSY;
case OPAL_NO_MEM: return -ENOMEM;
case OPAL_PERMISSION: return -EPERM;
--
2.13.2
next prev parent reply other threads:[~2017-06-29 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 6:54 [PATCH 0/5] Allow opal-async waiters to get interrupted Cyril Bur
2017-06-29 6:54 ` [PATCH 1/5] powerpc/opal: Make __opal_async_{get, release}_token() static Cyril Bur
2017-06-29 6:54 ` [PATCH 2/5] powerpc/opal: Rework the opal-async interface Cyril Bur
2017-06-29 6:54 ` [PATCH 3/5] powerpc/opal: Add opal_async_wait_response_interruptible() to opal-async Cyril Bur
2017-06-29 6:54 ` Cyril Bur [this message]
2017-06-29 6:54 ` [PATCH 5/5] mtd: powernv_flash: Use opal_async_wait_response_interruptible() Cyril Bur
2017-07-08 1:28 ` Brian Norris
2017-07-08 19:59 ` Benjamin Herrenschmidt
2017-07-09 23:58 ` Cyril Bur
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=20170629065413.19845-5-cyrilbur@gmail.com \
--to=cyrilbur@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stewart@linux.vnet.ibm.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).