From: Axel Heider <axelheider@gmx.de>
To: qemu-devel@nongnu.org
Subject: [PATCH 1/2] doc: Clarify serial parameters
Date: Tue, 3 Aug 2021 16:12:24 +0200 [thread overview]
Message-ID: <277c4838-aef4-97aa-e92b-8eb7c0056686@gmx.de> (raw)
There is a difference between 'null' and 'none'. Add a sentence to
highlight this, so this does not get mixed up.
Signed-off-by: Axel Heider <axelheider@gmx.de>
---
qemu-options.hx | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index 83aa59a920..e3f256fa72 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -3702,7 +3702,8 @@ SRST
[Linux only] Pseudo TTY (a new PTY is automatically allocated)
``none``
- No device is allocated.
+ No serial devices are allocated at all. Use ``null`` to disable a
+ specific serial device.
``null``
void device
--
2.17.1
next reply other threads:[~2021-08-03 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 14:12 Axel Heider [this message]
2021-09-01 13:25 ` [PATCH 1/2] doc: Clarify serial parameters Markus Armbruster
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=277c4838-aef4-97aa-e92b-8eb7c0056686@gmx.de \
--to=axelheider@gmx.de \
--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).