From: Stephen Hemminger <stephen@networkplumber.org>
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, jiri@mellanox.com, arkadis@mellanox.com
Subject: Re: [PATCH iproute2 0/2] add batch command support to devlink
Date: Sun, 12 Nov 2017 16:17:10 -0800 [thread overview]
Message-ID: <20171112161710.24a58754@xeon-e3> (raw)
In-Reply-To: <20171110062014.2693-1-ivecera@redhat.com>
On Fri, 10 Nov 2017 07:20:12 +0100
Ivan Vecera <ivecera@redhat.com> wrote:
> This patch series adds support for devlink commands batching. The first
> just removes a requirement to have declared 'resolve_hosts' variable in
> any command that use any function implemented in utils.c (it is really
> confusing to see this declaration in utils like bridge or devlink).
>
> Ivan Vecera (2):
> lib: make resolve_hosts variable common
> devlink: add batch command support
>
> bridge/bridge.c | 1 -
> devlink/devlink.c | 70 +++++++++++++++++++++++++++++++++++++++++++++++-------
> genl/genl.c | 1 -
> ip/ip.c | 1 -
> ip/rtmon.c | 1 -
> lib/utils.c | 1 +
> man/man8/devlink.8 | 16 +++++++++++++
> misc/arpd.c | 2 --
> misc/ss.c | 1 -
> tc/tc.c | 1 -
> 10 files changed, 79 insertions(+), 16 deletions(-)
>
Applied
prev parent reply other threads:[~2017-11-13 0:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 6:20 [PATCH iproute2 0/2] add batch command support to devlink Ivan Vecera
2017-11-10 6:20 ` [PATCH iproute2 1/2] lib: make resolve_hosts variable common Ivan Vecera
2017-11-10 6:20 ` [PATCH iproute2 2/2] devlink: add batch command support Ivan Vecera
2017-11-10 6:57 ` Leon Romanovsky
2017-11-10 7:10 ` Ivan Vecera
2017-11-10 19:47 ` Leon Romanovsky
2017-11-12 5:06 ` Jiri Pirko
2017-11-12 8:19 ` Leon Romanovsky
2017-11-12 8:21 ` Jiri Pirko
2017-11-13 0:16 ` Stephen Hemminger
2017-11-13 8:59 ` Leon Romanovsky
2017-11-12 5:08 ` Jiri Pirko
2017-11-13 0:17 ` Stephen Hemminger [this message]
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=20171112161710.24a58754@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=arkadis@mellanox.com \
--cc=ivecera@redhat.com \
--cc=jiri@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).