The changing mask note uses custom syntax (open asterisks), which triggers emphasis warnings as Sphinx confuses it as boldface: Documentation/s390/vfio-ap.rst:684: WARNING: Inline strong start-string without end-string. Documentation/s390/vfio-ap.rst:684: WARNING: Inline emphasis start-string without end-string. Use note directive instead. Link: https://lore.kernel.org/linux-next/20220721205937.10043b5f@xxxxxxxxxxxxxxxx/ Fixes: cb269e0aba7c3f ("s390/vfio-ap: update docs to include dynamic config support") Reported-by: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> Signed-off-by: Bagas Sanjaya <bagasdotme@xxxxxxxxx> --- Documentation/s390/vfio-ap.rst | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/Documentation/s390/vfio-ap.rst b/Documentation/s390/vfio-ap.rst index f4b8748ab9a8cd..7aea0afe2ef390 100644 --- a/Documentation/s390/vfio-ap.rst +++ b/Documentation/s390/vfio-ap.rst @@ -681,15 +681,17 @@ These are the steps: default drivers pool: adapter 0-15, domain 1 alternate drivers pool: adapter 16-255, domains 0, 2-255 - Note ***: - Changing a mask such that one or more APQNs will be taken from a vfio_ap - mediated device (see below) will fail with an error (EBUSY). A message - is logged to the kernel ring buffer which can be viewed with the 'dmesg' - command. The output identifies each APQN flagged as 'in use' and identifies - the vfio_ap mediated device to which it is assigned; for example: + .. note:: + + Changing a mask such that one or more APQNs will be taken from a vfio_ap + mediated device (see below) will fail with an error (EBUSY). A message + is logged to the kernel ring buffer which can be viewed with the 'dmesg' + command. The output identifies each APQN flagged as 'in use' and + identifies the vfio_ap mediated device to which it is assigned; for + example:: - Userspace may not re-assign queue 05.0054 already assigned to 62177883-f1bb-47f0-914d-32a22e3a8804 - Userspace may not re-assign queue 04.0054 already assigned to cef03c3c-903d-4ecc-9a83-40694cb8aee4 + Userspace may not re-assign queue 05.0054 already assigned to 62177883-f1bb-47f0-914d-32a22e3a8804 + Userspace may not re-assign queue 04.0054 already assigned to cef03c3c-903d-4ecc-9a83-40694cb8aee4 Securing the APQNs for our example ---------------------------------- -- An old man doll... just what I always wanted! - Clara
