diff options
| author | Markus Armbruster <armbru@redhat.com> | 2023-07-20 09:16:09 +0200 |
|---|---|---|
| committer | Markus Armbruster <armbru@redhat.com> | 2023-07-26 14:51:36 +0200 |
| commit | 9e272073e1c41acb3ba1e43b69c7a3f9c26089c2 (patch) | |
| tree | 177761a148e7ea59ce43bce26910b27c69216878 /qapi/qom.json | |
| parent | e27a9d628d7a9d0c31bc48c82937dd73dbbca01a (diff) | |
qapi: Reformat recent doc comments to conform to current conventions
Since commit a937b6aa739 (qapi: Reformat doc comments to conform to
current conventions), a number of comments not conforming to the
current formatting conventions were added. No problem, just sweep
the entire documentation once more.
To check the generated documentation does not change, I compared the
generated HTML before and after this commit with "wdiff -3". Finds no
differences. Comparing with diff is not useful, as the reflown
paragraphs are visible there.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20230720071610.1096458-7-armbru@redhat.com>
Diffstat (limited to 'qapi/qom.json')
| -rw-r--r-- | qapi/qom.json | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/qapi/qom.json b/qapi/qom.json index 7f92ea43e8..fa3e88c8e6 100644 --- a/qapi/qom.json +++ b/qapi/qom.json @@ -647,9 +647,10 @@ # selects a default alignment (currently the page size). # (default: 0) # -# @offset: the offset into the target file that the region starts at. You -# can use this option to back multiple regions with a single file. Must -# be a multiple of the page size. (default: 0) (since 8.1) +# @offset: the offset into the target file that the region starts at. +# You can use this option to back multiple regions with a single +# file. Must be a multiple of the page size. +# (default: 0) (since 8.1) # # @discard-data: if true, the file contents can be destroyed when QEMU # exits, to avoid unnecessarily flushing data to the backing file. @@ -662,7 +663,7 @@ # # @pmem: specifies whether the backing file specified by @mem-path is # in host persistent memory that can be accessed using the SNIA -# NVM programming model (e.g. Intel NVDIMM). +# NVM programming model (e.g. Intel NVDIMM). # # @readonly: if true, the backing file is opened read-only; if false, # it is opened read-write. (default: false) |