netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Vincent Bernat <vincent@bernat.ch>
Cc: Ido Schimmel <idosch@idosch.org>,
	Alce Lafranque <alce@lafranque.net>,
	netdev@vger.kernel.org, dsahern@gmail.com
Subject: Re: [PATCH iproute2] vxlan: add support for flowlab inherit
Date: Mon, 22 Jan 2024 16:10:05 -0800	[thread overview]
Message-ID: <20240122161005.29149777@hermes.local> (raw)
In-Reply-To: <d94453e7-a56d-4aa5-8e5f-3d9a590fd968@bernat.ch>

On Mon, 22 Jan 2024 22:11:32 +0100
Vincent Bernat <vincent@bernat.ch> wrote:

> On 2024-01-22 13:24, Ido Schimmel wrote:
> > s/flowlab/flowlabel/ in subject
> > 
> > My understanding is that new features should be targeted at
> > iproute2-next. See the README.  
> 
> You may be more familiar than I am about this, but since the kernel part 
> is already in net, it should go to the stable branch of iproute2.

There is no stable branch. Only current (based of Linus tree)
and next (for net-next kernel).

  reply	other threads:[~2024-01-23  0:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-20 12:44 [PATCH iproute2] vxlan: add support for flowlab inherit Alce Lafranque
2024-01-22 12:24 ` Ido Schimmel
2024-01-22 21:11   ` Vincent Bernat
2024-01-23  0:10     ` Stephen Hemminger [this message]
2024-01-23  0:29       ` David Ahern
2024-01-23  0:41   ` David Ahern
2024-01-23  7:58     ` Vincent Bernat
2024-01-23 16:19       ` David Ahern
2024-01-24 22:00         ` Vincent Bernat
2024-01-25 15:50           ` David Ahern
2024-01-26  6:28             ` Vincent Bernat
2024-01-26 17:17               ` David Ahern
2024-01-28 12:35                 ` Ido Schimmel
2024-01-28 14:28                   ` Vincent Bernat
2024-01-29 18:44                   ` David Ahern

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=20240122161005.29149777@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=alce@lafranque.net \
    --cc=dsahern@gmail.com \
    --cc=idosch@idosch.org \
    --cc=netdev@vger.kernel.org \
    --cc=vincent@bernat.ch \
    /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).