secvar_api: check that enqueue_update writes successfully before retu…

…rning success

The return code to the storage driver's write function was previously
being ignored, so failures to write were not propogated to the API
consumer. This patch fixes secvar_enqueue_update() to properly return
the expected OPAL_HARDWARE return code if the storage driver's write
function returns an error.

Signed-off-by: Eric Richter <erichte@linux.ibm.com>
Signed-off-by: Oliver O'Halloran <oohall@gmail.com>

libstb/secvar/secvar_api.c

@@ -151,8 +151,9 @@ static int64_t opal_secvar_enqueue_update(const char *key, uint64_t key_len, voi
 	list_add_tail(&update_bank, &node->link);
 
 out:
-	secvar_storage.write_bank(&update_bank, SECVAR_UPDATE_BANK);
-
-	return OPAL_SUCCESS;
+	if (secvar_storage.write_bank(&update_bank, SECVAR_UPDATE_BANK))
+		return OPAL_HARDWARE;
+	else
+		return OPAL_SUCCESS;
 }
 opal_call(OPAL_SECVAR_ENQUEUE_UPDATE, opal_secvar_enqueue_update, 4);