public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Roopa Prabhu <roopa@cumulusnetworks.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: dsa@cumulusnetworks.com, buytenh@wantstofly.org,
	ebiederm@xmission.com, rshearma@brocade.com,
	simon.horman@netronome.com, tom@herbertland.com, tgraf@suug.ch,
	olivier.dugeon@orange.com
Subject: Re: [PATCH net-next 0/3] lwtunnel, mpls fragmentation and gso fixes
Date: Thu, 11 Aug 2016 06:49:53 -0700	[thread overview]
Message-ID: <57AC8281.2040504@cumulusnetworks.com> (raw)
In-Reply-To: <1470897812-8213-1-git-send-email-roopa@cumulusnetworks.com>

On 8/10/16, 11:43 PM, Roopa Prabhu wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> This series fixes a few issues around mtu and fragmentation
> for tunnels using lwtunnel output redirect and also fixes
> a few gso issues recently reported by Lennert Buytenhek.
>
> David Ahern (2):
>   net: mpls fixes for GSO
>   net: veth: set features for MPLS
>
> Roopa Prabhu (1):
>   lwtunnel: xmit redirect
>
>
I see kbuild test robot reporting some compile errors.
I must have screwed up the submission last night and
in a hurry to get some more review i did not test it with other configs. sorry about that.
will fix these + any other pending review comments and send out a v2 later today.

thanks,
Roopa

      parent reply	other threads:[~2016-08-11 13:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11  6:43 [PATCH net-next 0/3] lwtunnel, mpls fragmentation and gso fixes Roopa Prabhu
2016-08-11  6:43 ` [PATCH net-next 1/3] lwtunnel: xmit redirect Roopa Prabhu
2016-08-11  7:04   ` kbuild test robot
2016-08-11  7:07   ` kbuild test robot
2016-08-11  6:43 ` [PATCH net-next 2/3] net: mpls fixes for GSO Roopa Prabhu
2016-08-11  7:47   ` Simon Horman
2016-08-11 13:30     ` Simon Horman
2016-08-11 13:47       ` David Ahern
2016-08-11  6:43 ` [PATCH net-next 3/3] net: veth: set features for MPLS Roopa Prabhu
2016-08-11 13:49 ` Roopa Prabhu [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=57AC8281.2040504@cumulusnetworks.com \
    --to=roopa@cumulusnetworks.com \
    --cc=buytenh@wantstofly.org \
    --cc=davem@davemloft.net \
    --cc=dsa@cumulusnetworks.com \
    --cc=ebiederm@xmission.com \
    --cc=netdev@vger.kernel.org \
    --cc=olivier.dugeon@orange.com \
    --cc=rshearma@brocade.com \
    --cc=simon.horman@netronome.com \
    --cc=tgraf@suug.ch \
    --cc=tom@herbertland.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox