[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200325.193016.1654692564933635575.davem@davemloft.net>
Date: Wed, 25 Mar 2020 19:30:16 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: andrea.mayer@...roma2.it
Cc: kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org,
dav.lebrun@...il.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, leon@...nel.org, ast@...nel.org,
daniel@...earbox.net, kafai@...com, songliubraving@...com,
yhs@...com, andriin@...com, bpf@...r.kernel.org,
paolo.lungaroni@...t.it, ahmed.abdelsalam@...i.it
Subject: Re: [net-next] seg6: add support for optional attributes during
behavior construction
From: Andrea Mayer <andrea.mayer@...roma2.it>
Date: Thu, 19 Mar 2020 19:36:41 +0100
> Messy code and complicated tricks may arise from this approach.
People taking advantage of this new flexibility will write
applications that DO NOT WORK on older kernels.
I think we are therefore stuck with the current optional attribute
semantics, sorry.
Powered by blists - more mailing lists