From: Stephen Hemminger <stephen@networkplumber.org>
To: Arkadi Sharshevsky <arkadis@mellanox.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, mlxsw@mellanox.com
Subject: Re: [PATCH iproute2] devlink: Ignore unknown attributes
Date: Thu, 18 Jan 2018 16:32:38 -0800 [thread overview]
Message-ID: <20180118163238.7eebf4bb@xeon-e3> (raw)
In-Reply-To: <1516195680-33683-1-git-send-email-arkadis@mellanox.com>
On Wed, 17 Jan 2018 15:28:00 +0200
Arkadi Sharshevsky <arkadis@mellanox.com> wrote:
> In case of extending the UAPI old packages would break.
>
> Signed-off-by: Arkadi Sharshevsky <arkadis@mellanox.com>
Looks like good future proofing.
Applied.
next prev parent reply other threads:[~2018-01-19 0:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 13:28 [PATCH iproute2] devlink: Ignore unknown attributes Arkadi Sharshevsky
2018-01-17 13:37 ` Jiri Pirko
2018-01-19 0:32 ` Stephen Hemminger [this message]
2018-01-19 4:42 ` David Ahern
2018-01-19 22:02 ` Stephen Hemminger
2018-01-19 22:27 ` David Ahern
2018-01-19 23:40 ` Stephen Hemminger
2018-01-20 0:00 ` 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=20180118163238.7eebf4bb@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=arkadis@mellanox.com \
--cc=davem@davemloft.net \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.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).