All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amine Kherbouche <amine.kherbouche@6wind.com>
To: David Lamparter <equinox@diac24.net>,
	netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Cc: roopa@cumulusnetworks.com, stephen@networkplumber.org
Subject: Re: [RFC net-next v2] bridge lwtunnel, VPLS & NVGRE
Date: Tue, 19 Sep 2017 16:46:38 +0200	[thread overview]
Message-ID: <6b7cdb61-9c24-3fcb-d23c-f08ca2144ec9@6wind.com> (raw)
In-Reply-To: <6a538120-1941-7e81-c942-e97adeff2e3d@6wind.com>

Hi David,

What's next ? do you plan to send a v3 or should I do it ?

On 09/11/2017 10:02 AM, Amine Kherbouche wrote:
> Hi David,
>
> Do you plan to send a v3?
>
> On 21/08/2017 18:15, David Lamparter wrote:
>> Hi all,
>>
>>
>> this is an update on the earlier "[RFC net-next] VPLS support".  Note
>> I've changed the subject lines on some of the patches to better reflect
>> what they really do (tbh the earlier subject lines were crap.)
>>
>> As previously, iproute2 / FRR patches are at:
>> - https://github.com/eqvinox/vpls-iproute2
>> - https://github.com/opensourcerouting/frr/commits/vpls
>> while this patchset is also available at:
>> - https://github.com/eqvinox/vpls-linux-kernel
>> (but please be aware that I'm amending and rebasing commits)

WARNING: multiple messages have this Message-ID (diff)
From: Amine Kherbouche <amine.kherbouche@6wind.com>
To: David Lamparter <equinox@diac24.net>,
	netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Cc: roopa@cumulusnetworks.com
Subject: Re: [Bridge] [RFC net-next v2] bridge lwtunnel, VPLS & NVGRE
Date: Tue, 19 Sep 2017 14:46:52 -0000	[thread overview]
Message-ID: <6b7cdb61-9c24-3fcb-d23c-f08ca2144ec9@6wind.com> (raw)
In-Reply-To: <6a538120-1941-7e81-c942-e97adeff2e3d@6wind.com>

Hi David,

What's next ? do you plan to send a v3 or should I do it ?

On 09/11/2017 10:02 AM, Amine Kherbouche wrote:
> Hi David,
>
> Do you plan to send a v3?
>
> On 21/08/2017 18:15, David Lamparter wrote:
>> Hi all,
>>
>>
>> this is an update on the earlier "[RFC net-next] VPLS support".  Note
>> I've changed the subject lines on some of the patches to better reflect
>> what they really do (tbh the earlier subject lines were crap.)
>>
>> As previously, iproute2 / FRR patches are at:
>> - https://github.com/eqvinox/vpls-iproute2
>> - https://github.com/opensourcerouting/frr/commits/vpls
>> while this patchset is also available at:
>> - https://github.com/eqvinox/vpls-linux-kernel
>> (but please be aware that I'm amending and rebasing commits)

  reply	other threads:[~2017-09-19 14:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 17:15 [RFC net-next v2] bridge lwtunnel, VPLS & NVGRE David Lamparter
2017-08-21 17:15 ` [Bridge] " David Lamparter
2017-08-21 17:15 ` [PATCH 1/6] bridge: lwtunnel support in FDB David Lamparter
2017-08-21 17:15   ` [Bridge] " David Lamparter
2017-08-21 17:15 ` [PATCH 2/6] bridge: lwtunnel netlink interface David Lamparter
2017-08-21 17:15   ` [Bridge] " David Lamparter
2017-08-21 17:15 ` [PATCH 3/6] gretap: support lwtunnel under bridge (NVGRE) David Lamparter
2017-08-21 17:15   ` [Bridge] " David Lamparter
2017-08-21 17:15 ` [PATCH 4/6] mpls: split forwarding path on rx/tx boundary David Lamparter
2017-08-21 17:15   ` [Bridge] " David Lamparter
2017-08-21 17:15 ` [PATCH 5/6] mpls: add VPLS entry points David Lamparter
2017-08-21 17:15   ` [Bridge] " David Lamparter
2017-08-21 17:15 ` [PATCH 6/6] mpls: VPLS support David Lamparter
2017-08-21 17:15   ` [Bridge] " David Lamparter
2017-08-28  9:21   ` Amine Kherbouche
2017-08-28  9:21     ` [Bridge] " Amine Kherbouche
2017-08-22  0:01 ` [RFC net-next v2] bridge lwtunnel, VPLS & NVGRE Stephen Hemminger
2017-08-22  0:01   ` [Bridge] " Stephen Hemminger
2017-08-22  0:29   ` David Lamparter
2017-08-22  0:29     ` [Bridge] " David Lamparter
2017-08-22 11:01   ` Nikolay Aleksandrov
2017-08-22 11:01     ` [Bridge] " Nikolay Aleksandrov
2017-08-22 11:32     ` David Lamparter
2017-08-22 11:32       ` [Bridge] " David Lamparter
2017-08-22 11:55       ` Nikolay Aleksandrov
2017-08-22 11:55         ` [Bridge] " Nikolay Aleksandrov
2017-08-22 12:06         ` David Lamparter
2017-08-22 12:06           ` [Bridge] " David Lamparter
2017-08-22  4:43 ` Roopa Prabhu
2017-08-22  4:43   ` [Bridge] " Roopa Prabhu
2017-08-22 11:24   ` David Lamparter
2017-08-22 11:24     ` [Bridge] " David Lamparter
2017-09-11  8:02 ` Amine Kherbouche
2017-09-11  8:02   ` [Bridge] " Amine Kherbouche
2017-09-19 14:46   ` Amine Kherbouche [this message]
2017-09-19 14:46     ` Amine Kherbouche

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=6b7cdb61-9c24-3fcb-d23c-f08ca2144ec9@6wind.com \
    --to=amine.kherbouche@6wind.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=equinox@diac24.net \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=stephen@networkplumber.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 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.