From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: [PATCH 6/6] docs/devel/qom: Avoid long lines
Date: Fri, 2 Oct 2020 22:54:24 -0400 [thread overview]
Message-ID: <20201003025424.199291-7-ehabkost@redhat.com> (raw)
In-Reply-To: <20201003025424.199291-1-ehabkost@redhat.com>
Long code lines don't look good in the rendered documents, make
them shorter.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
docs/devel/qom.rst | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/docs/devel/qom.rst b/docs/devel/qom.rst
index 0c610e20d62..42d0dc4f4da 100644
--- a/docs/devel/qom.rst
+++ b/docs/devel/qom.rst
@@ -284,7 +284,8 @@ in the header file:
.. code-block:: c
:caption: Declaring a simple type
- OBJECT_DECLARE_SIMPLE_TYPE(MyDevice, my_device, MY_DEVICE, DEVICE)
+ OBJECT_DECLARE_SIMPLE_TYPE(MyDevice, my_device,
+ MY_DEVICE, DEVICE)
This is equivalent to the following:
@@ -360,7 +361,8 @@ This accepts an array of interface type names.
OBJECT_DEFINE_TYPE_WITH_INTERFACES(MyDevice, my_device,
MY_DEVICE, DEVICE,
- { TYPE_USER_CREATABLE }, { NULL })
+ { TYPE_USER_CREATABLE },
+ { NULL })
If the type is not intended to be instantiated, then then
the OBJECT_DEFINE_ABSTRACT_TYPE() macro can be used instead:
@@ -368,7 +370,8 @@ the OBJECT_DEFINE_ABSTRACT_TYPE() macro can be used instead:
.. code-block:: c
:caption: Defining a simple abstract type
- OBJECT_DEFINE_ABSTRACT_TYPE(MyDevice, my_device, MY_DEVICE, DEVICE)
+ OBJECT_DEFINE_ABSTRACT_TYPE(MyDevice, my_device,
+ MY_DEVICE, DEVICE)
--
2.26.2
next prev parent reply other threads:[~2020-10-03 2:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 2:54 [PATCH 0/6] qom documentation fixes Eduardo Habkost
2020-10-03 2:54 ` [PATCH 1/6] qom: Fix DECLARE_*CHECKER documentation Eduardo Habkost
2020-10-03 17:56 ` Philippe Mathieu-Daudé
2020-10-03 2:54 ` [PATCH 2/6] docs/devel/qom: Fix indentation of bulleted list Eduardo Habkost
2020-10-03 2:54 ` [PATCH 3/6] docs/devel/qom: Fix indentation of code blocks Eduardo Habkost
2020-10-03 2:54 ` [PATCH 4/6] docs/devel/qom: Use *emphasis* for emphasis Eduardo Habkost
2020-10-03 17:55 ` Philippe Mathieu-Daudé
2020-10-03 2:54 ` [PATCH 5/6] docs/devel/qom: Remove usage of <code> Eduardo Habkost
2020-10-03 9:03 ` Paolo Bonzini
2020-10-03 2:54 ` Eduardo Habkost [this message]
2020-10-03 17:56 ` [PATCH 6/6] docs/devel/qom: Avoid long lines Philippe Mathieu-Daudé
2020-10-03 9:03 ` [PATCH 0/6] qom documentation fixes Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201003025424.199291-7-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).