Commit 785724e81c for qemu.org

commit 785724e81c35bb5bb13400d8424e26671a0fd74f
Author: J. Neuschäfer <j.neuschaefer@9elements.com>
Date:   Wed May 13 17:06:40 2026 +0200

    docs/devel: Fix formatting of `Error **`

    Since the ReST conversion, Error ** is expressed as Error ``*````*``, which is
    rendered in HTML as Error *````*. Fix it so the HTML output resembles the
    intended C syntax.

    Fixes: 336a7451e8 ("docs: convert README, CODING_STYLE and HACKING to RST syntax")
    Signed-off-by: J. Neuschäfer <j.neuschaefer@9elements.com>
    Tested-by: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
    Reviewed-by: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
    Link: https://lore.kernel.org/qemu-devel/20260513-error-v1-1-49fa04bc5c22@9elements.com
    Signed-off-by: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>

diff --git a/docs/devel/style.rst b/docs/devel/style.rst
index 12e509d10d..b8edcf9316 100644
--- a/docs/devel/style.rst
+++ b/docs/devel/style.rst
@@ -784,10 +784,10 @@ error, non-negative / -errno, non-null / null, or Error objects.
 Example: when a function returns a non-null pointer on success, and it
 can fail only in one way (as far as the caller is concerned), returning
 null on failure is just fine, and certainly simpler and a lot easier on
-the eyes than propagating an Error object through an Error ``*````*`` parameter.
+the eyes than propagating an Error object through an ``Error **`` parameter.

 Example: when a function's callers need to report details on failure
-only the function really knows, use Error ``*````*``, and set suitable errors.
+only the function really knows, use ``Error **``, and set suitable errors.

 Do not report an error to the user when you're also returning an error
 for somebody else to handle.  Leave the reporting to the place that