linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: andrea.mayer@uniroma2.it
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
	dav.lebrun@gmail.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, leon@kernel.org, ast@kernel.org,
	daniel@iogearbox.net, kafai@fb.com, songliubraving@fb.com,
	yhs@fb.com, andriin@fb.com, bpf@vger.kernel.org,
	paolo.lungaroni@cnit.it, ahmed.abdelsalam@gssi.it
Subject: Re: [net-next] seg6: add support for optional attributes during behavior construction
Date: Wed, 25 Mar 2020 19:30:16 -0700 (PDT)	[thread overview]
Message-ID: <20200325.193016.1654692564933635575.davem@davemloft.net> (raw)
In-Reply-To: <20200319183641.29608-1-andrea.mayer@uniroma2.it>

From: Andrea Mayer <andrea.mayer@uniroma2.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.

  reply	other threads:[~2020-03-26  2:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 18:36 [net-next] seg6: add support for optional attributes during behavior construction Andrea Mayer
2020-03-26  2:30 ` David Miller [this message]
2020-03-30 23:23   ` Stefano Salsano
2020-03-31  0:49     ` David Miller
2020-03-31  1:32       ` Stefano Salsano
  -- strict thread matches above, loose matches on Subject: below --
2020-02-03 14:36 Andrea Mayer
2020-02-03 15:08 ` Leon Romanovsky
2020-02-05 16:37   ` Andrea Mayer
2020-01-27 19:04 Andrea Mayer
2020-01-29 10:13 ` David Miller

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=20200325.193016.1654692564933635575.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ahmed.abdelsalam@gssi.it \
    --cc=andrea.mayer@uniroma2.it \
    --cc=andriin@fb.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dav.lebrun@gmail.com \
    --cc=kafai@fb.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paolo.lungaroni@cnit.it \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.com \
    --cc=yoshfuji@linux-ipv6.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 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).