| Message ID | 20191209011448.19319-12-oohall@gmail.com |
|---|---|
| State | Accepted |
| Headers | show |
| Series | [01/18] doc: Add skiboot-5.2.0 ref | expand |
| Context | Check | Description |
|---|---|---|
| snowpatch_ozlabs/apply_patch | warning | Failed to apply on branch master (d75e82dbfbb9443efeb3f9a5921ac23605aab469) |
| snowpatch_ozlabs/apply_patch | fail | Failed to apply to any branch |
diff --git a/doc/opal-api/opal-handle-hmi-98-166.rst b/doc/opal-api/opal-handle-hmi-98-166.rst index 5959e5e90194..5b75144dc0bb 100644 --- a/doc/opal-api/opal-handle-hmi-98-166.rst +++ b/doc/opal-api/opal-handle-hmi-98-166.rst @@ -117,7 +117,7 @@ event was generated. This information will help OS to take respective actions. In case where opal hmi handler is unable to recover from TOD or TB errors, -it would flag :ref:`OPAL_HMI_FLAGS_TOD_TB_FAIL` to indicate OS that TB is +it would flag ``OPAL_HMI_FLAGS_TOD_TB_FAIL`` to indicate OS that TB is dead. This information then can be used by OS to make sure that the functions relying on TB value (e.g. udelay()) are aware of TB not ticking. This will avoid OS getting stuck or hang during its way to panic path.
A definition for this flag is provided below in a code block. It's not an OPAL call so there's no ref to it and we get a warning. Signed-off-by: Oliver O'Halloran <oohall@gmail.com> --- doc/opal-api/opal-handle-hmi-98-166.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)