From: Jason Wang <jasowang@redhat.com>
To: Stefan Weil <sw@weilnetz.de>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Henrik Johansson <henrikjohansson@rocketmail.com>
Subject: Re: [PATCH] l2tpv3: fix RFC number typo in qemu-options.hx
Date: Mon, 2 Mar 2020 13:48:58 +0800 [thread overview]
Message-ID: <189c4909-a269-6c4f-bb62-87b29a01ff83@redhat.com> (raw)
In-Reply-To: <ae5cd213-ada2-1b20-064c-a0bc63d3622d@weilnetz.de>
On 2020/2/29 下午7:57, Stefan Weil wrote:
> Am 29.02.20 um 12:17 schrieb Stefan Hajnoczi:
>
>> The L2TPv3 RFC number is 3931:
>> https://tools.ietf.org/html/rfc3931
>>
>> Reported-by: Henrik Johansson <henrikjohansson@rocketmail.com>
>> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>> ---
>> qemu-options.hx | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/qemu-options.hx b/qemu-options.hx
>> index ac315c1ac4..55a539e04f 100644
>> --- a/qemu-options.hx
>> +++ b/qemu-options.hx
>> @@ -2330,7 +2330,7 @@ DEF("netdev", HAS_ARG, QEMU_OPTION_netdev,
>> " Linux kernel 3.3+ as well as most routers can talk\n"
>> " L2TPv3. This transport allows connecting a VM to a VM,\n"
>> " VM to a router and even VM to Host. It is a nearly-universal\n"
>> - " standard (RFC3391). Note - this implementation uses static\n"
>> + " standard (RFC3931). Note - this implementation uses static\n"
>> " pre-configured tunnels (same as the Linux kernel).\n"
>> " use 'src=' to specify source address\n"
>> " use 'dst=' to specify destination address\n"
>> @@ -2737,7 +2737,7 @@ Example (send packets from host's 1.2.3.4):
>> @end example
>>
>> @item -netdev l2tpv3,id=@var{id},src=@var{srcaddr},dst=@var{dstaddr}[,srcport=@var{srcport}][,dstport=@var{dstport}],txsession=@var{txsession}[,rxsession=@var{rxsession}][,ipv6][,udp][,cookie64][,counter][,pincounter][,txcookie=@var{txcookie}][,rxcookie=@var{rxcookie}][,offset=@var{offset}]
>> -Configure a L2TPv3 pseudowire host network backend. L2TPv3 (RFC3391) is a
>> +Configure a L2TPv3 pseudowire host network backend. L2TPv3 (RFC3931) is a
>> popular protocol to transport Ethernet (and other Layer 2) data frames between
>> two systems. It is present in routers, firewalls and the Linux kernel
>> (from version 3.3 onwards).
>
> Thank you, Stefan and Henrik.
>
> Reviewed-by: Stefan Weil <sw@weilnetz.de>
>
Applied.
Thanks
prev parent reply other threads:[~2020-03-02 5:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 11:17 [PATCH] l2tpv3: fix RFC number typo in qemu-options.hx Stefan Hajnoczi
2020-02-29 11:57 ` Stefan Weil
2020-03-02 5:48 ` Jason Wang [this message]
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=189c4909-a269-6c4f-bb62-87b29a01ff83@redhat.com \
--to=jasowang@redhat.com \
--cc=henrikjohansson@rocketmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).