All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: anton.ivanov@kot-begemot.co.uk, qemu-devel@nongnu.org
Cc: Anton Ivanov <antivano@cisco.com>,
	pbonzini@redhat.com, afaerber@suse.de, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] net: L2TPv3 transport
Date: Mon, 10 Mar 2014 10:06:02 -0600	[thread overview]
Message-ID: <531DE2EA.8000101@redhat.com> (raw)
In-Reply-To: <1394451098-296108-1-git-send-email-anton.ivanov@kot-begemot.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1751 bytes --]

On 03/10/2014 05:31 AM, anton.ivanov@kot-begemot.co.uk wrote:
> From: Anton Ivanov <antivano@cisco.com>

When sending revisions of a patch sent earlier, be sure to include
'PATCHv2' (or higher, as appropriate) in the subject,...

> 
> This tranport allows to connect a qemu nic to a static Ethernet
> over L2TPv3 tunnel. The transport supports all options present
> in the linux kernel implementation. It allows qemu to connect
> to any linux host running kernel 3.3+, most routers and network
> 
> Signed-off-by: Anton Ivanov <antivano@cisco.com>
> ---

...and describe what changed from v1 after the --- separator.  That way,
earlier reviewers will know what differences to look for, instead of
assuming it is a brand new patch.

> +++ b/qapi-schema.json
> @@ -2940,6 +2940,60 @@
>      '*localaddr': 'str',
>      '*udp':       'str' } }
>  
> +# @NetdevL2TPv3Options

Missing a ## line prior to the struct name.

> +# @pincounter: #optional pin sequence counter to zero - workaround for buggy implementations or networks with packet reorder

Super long line.  Please wrap at 80 columns.

> +#
> +# @txcookie: #optional 32 or 64 bit transmit cookie
> +#
> +# @rxcookie: #optional 32 or 64 bit receive cookie
> +#
> +# @txsession: 32 bit transmit session
> +#
> +# @rxsession: 32 bit receive session - if not specified set to the same value as transmit
> +#
> +# @optional: additional offset - allows the insertion of additional application-specific data before the packet payload

Another long line.  Also, you don't have a variable named 'optional';
you probably meant '@offset: #optional'.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  parent reply	other threads:[~2014-03-10 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 11:31 [Qemu-devel] [PATCH] net: L2TPv3 transport anton.ivanov
2014-03-10 15:05 ` Stefan Hajnoczi
2014-03-10 15:09   ` Anton Ivanov (antivano)
2014-03-10 16:06 ` Eric Blake [this message]
2014-03-10 16:31   ` Anton Ivanov

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=531DE2EA.8000101@redhat.com \
    --to=eblake@redhat.com \
    --cc=afaerber@suse.de \
    --cc=antivano@cisco.com \
    --cc=anton.ivanov@kot-begemot.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.