PEL: Get rid of the enum for a maint procedure
It simplifies the code to just use the string name of the procedure as defined
by the message registry schema, and make it be less maintenance to add
new procedures in the future, especially if they come from the registry
so the enum isn't even needed.
This will also make it the same as upcoming support for symbolic FRU
callouts, which will always just come from the registry or an external
user so would not need an enum.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ia8550235678ba1fc717a6b0875e2d7ff3888bfec
diff --git a/extensions/openpower-pels/callout.hpp b/extensions/openpower-pels/callout.hpp
index c8bb0a3..6b7dbc7 100644
--- a/extensions/openpower-pels/callout.hpp
+++ b/extensions/openpower-pels/callout.hpp
@@ -87,9 +87,10 @@
* out maintenance procedure.
*
* @param[in] priority - The priority of the callout
- * @param[in] procedure - The maintenance procedure
+ * @param[in] procedureFromRegistry - The maintenance procedure name
+ * as defined in the message registry.
*/
- Callout(CalloutPriority priority, MaintProcedure procedure);
+ Callout(CalloutPriority priority, const std::string& procedureFromRegistry);
/**
* @brief Returns the size of this object when flattened into a PEL