From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: Jason Wang <jasowang@redhat.com>
Subject: [Qemu-devel] [PATCH 2/8] qemu-options: Fix markup of -netdev l2tpv3
Date: Mon, 2 Oct 2017 16:03:01 +0200 [thread overview]
Message-ID: <20171002140307.5292-3-armbru@redhat.com> (raw)
In-Reply-To: <20171002140307.5292-1-armbru@redhat.com>
The table of option parameters lacks @table and @end table. The
parameters become items in the enclosing table of options. Screwed up
when l2tpv3 was added in commit 3fb69aa. Fix the obvious way.
Cc: Jason Wang <jasowang@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
---
qemu-options.hx | 2 ++
1 file changed, 2 insertions(+)
diff --git a/qemu-options.hx b/qemu-options.hx
index 0fed2fc009..39f0e1b990 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -2367,6 +2367,7 @@ two systems. It is present in routers, firewalls and the Linux kernel
This transport allows a VM to communicate to another VM, router or firewall directly.
+@table @option
@item src=@var{srcaddr}
source address (mandatory)
@item dst=@var{dstaddr}
@@ -2394,6 +2395,7 @@ draft-mkonstan-l2tpext-keyed-ipv6-tunnel-00
networks which have packet reorder.
@item offset=@var{offset}
Add an extra offset between header and data
+@end table
For example, to attach a VM running on host 4.3.2.1 via L2TPv3 to the bridge br-lan
on the remote Linux host 1.2.3.4:
--
2.13.6
next prev parent reply other threads:[~2017-10-02 14:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 14:02 [Qemu-devel] [PATCH 0/8] qemu-options: Texinfo and --help fixes Markus Armbruster
2017-10-02 14:03 ` [Qemu-devel] [PATCH 1/8] qemu-options: Remove stray colons from output of --help Markus Armbruster
2017-10-02 15:25 ` Eric Blake
2017-10-04 10:13 ` Marc-André Lureau
2017-10-02 14:03 ` Markus Armbruster [this message]
2017-10-02 15:28 ` [Qemu-devel] [PATCH 2/8] qemu-options: Fix markup of -netdev l2tpv3 Eric Blake
2017-10-04 10:13 ` Marc-André Lureau
2017-10-02 14:03 ` [Qemu-devel] [PATCH 3/8] qemu-options qemu-doc: Move "Device URL Syntax" to qemu-doc Markus Armbruster
2017-10-02 15:31 ` Eric Blake
2017-10-04 10:12 ` Marc-André Lureau
2017-10-04 10:39 ` ronnie sahlberg
2017-10-04 12:53 ` Markus Armbruster
2017-10-02 14:03 ` [Qemu-devel] [PATCH 4/8] qemu-options: Move -iscsi under "Block device options" Markus Armbruster
2017-10-02 15:32 ` Eric Blake
2017-10-04 10:12 ` Marc-André Lureau
2017-10-04 10:33 ` ronnie sahlberg
2017-10-02 14:03 ` [Qemu-devel] [PATCH 5/8] qemu-options: Add missing -iscsi Texinfo documentation Markus Armbruster
2017-10-02 15:33 ` Eric Blake
2017-10-04 10:12 ` Marc-André Lureau
2017-10-04 13:02 ` Markus Armbruster
2017-10-04 10:31 ` ronnie sahlberg
2017-10-02 14:03 ` [Qemu-devel] [PATCH 6/8] qemu-options: Polish section "TPM device options" Markus Armbruster
2017-10-02 15:34 ` Eric Blake
2017-10-04 10:12 ` Marc-André Lureau
2017-10-02 14:03 ` [Qemu-devel] [PATCH 7/8] qemu-options: Polish section "Character " Markus Armbruster
2017-10-02 15:34 ` Eric Blake
2017-10-04 10:12 ` Marc-André Lureau
2017-10-02 14:03 ` [Qemu-devel] [PATCH 8/8] qemu-options: Belatedly document --watchdog-action inject-nmi Markus Armbruster
2017-10-02 15:35 ` Eric Blake
2017-10-04 10:12 ` Marc-André Lureau
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=20171002140307.5292-3-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=jasowang@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).