From: Stephen Hemminger <stephen@networkplumber.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, idosch@mellanox.com,
eladr@mellanox.com, yotamg@mellanox.com, ogerlitz@mellanox.com,
roopa@cumulusnetworks.com, nikolay@cumulusnetworks.com,
jhs@mojatatu.com, john.fastabend@gmail.com, rami.rosen@intel.com,
gospo@cumulusnetworks.com, sfeldma@gmail.com
Subject: Re: [patch iproute2 00/11] devlink: add support for shared buffer configuration and control
Date: Fri, 13 May 2016 14:44:35 -0700 [thread overview]
Message-ID: <20160513144435.5a29a051@xeon-e3> (raw)
In-Reply-To: <1460706713-5942-1-git-send-email-jiri@resnulli.us>
On Fri, 15 Apr 2016 09:51:42 +0200
Jiri Pirko <jiri@resnulli.us> wrote:
> From: Jiri Pirko <jiri@mellanox.com>
>
> Jiri Pirko (11):
> devlink: fix "devlink port" help message
> list: add list_for_each_entry_reverse macro
> list: add list_add_tail helper
> devlink: introduce pr_out_port_handle helper
> devlink: introduce helper to print out nice names (ifnames)
> devlink: split dl_argv_parse_put to parse and put parts
> devlink: introduce dump filtering function
> devlink: allow to parse both devlink and port handle in the same time
> devlink: implement shared buffer support
> devlink: implement shared buffer occupancy control
> devlink: add manpage for shared buffer
>
> devlink/devlink.c | 1310 +++++++++++++++++++++++++++++++++++++++++---
> include/linux/devlink.h | 63 +++
> include/list.h | 16 +
> man/man8/devlink-dev.8 | 2 +
> man/man8/devlink-monitor.8 | 1 +
> man/man8/devlink-port.8 | 2 +
> man/man8/devlink-sb.8 | 313 +++++++++++
> man/man8/devlink.8 | 5 +
> 8 files changed, 1636 insertions(+), 76 deletions(-)
> create mode 100644 man/man8/devlink-sb.8
>
I had to revert all this. Because you are depending on headers in net-next.
Please resubmit against net-next tree of iproute.
next prev parent reply other threads:[~2016-05-13 21:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 7:51 [patch iproute2 00/11] devlink: add support for shared buffer configuration and control Jiri Pirko
2016-04-15 7:51 ` [patch iproute2 01/11] devlink: fix "devlink port" help message Jiri Pirko
2016-04-15 7:51 ` [patch iproute2 02/11] list: add list_for_each_entry_reverse macro Jiri Pirko
2016-04-15 7:51 ` [patch iproute2 03/11] list: add list_add_tail helper Jiri Pirko
2016-04-15 7:51 ` [patch iproute2 04/11] devlink: introduce pr_out_port_handle helper Jiri Pirko
2016-04-15 7:51 ` [patch iproute2 05/11] devlink: introduce helper to print out nice names (ifnames) Jiri Pirko
2016-04-15 7:51 ` [patch iproute2 06/11] devlink: split dl_argv_parse_put to parse and put parts Jiri Pirko
2016-04-15 7:51 ` [patch iproute2 07/11] devlink: introduce dump filtering function Jiri Pirko
2016-04-15 7:51 ` [patch iproute2 08/11] devlink: allow to parse both devlink and port handle in the same time Jiri Pirko
2016-04-15 7:51 ` [patch iproute2 09/11] devlink: implement shared buffer support Jiri Pirko
2016-04-15 7:51 ` [patch iproute2 10/11] devlink: implement shared buffer occupancy control Jiri Pirko
2016-04-15 7:51 ` [patch iproute2 11/11] devlink: add manpage for shared buffer Jiri Pirko
2016-04-19 15:01 ` [patch iproute2 00/11] devlink: add support for shared buffer configuration and control Stephen Hemminger
2016-05-13 21:44 ` Stephen Hemminger [this message]
2016-05-14 13:21 ` [iproute2 net-next repost 1/2] devlink: implement shared buffer support Jiri Pirko
2016-05-14 13:21 ` [iproute2 net-next repost 2/2] devlink: implement shared buffer occupancy control Jiri Pirko
2016-05-16 18:23 ` [iproute2 net-next repost 1/2] devlink: implement shared buffer support Stephen Hemminger
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=20160513144435.5a29a051@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=eladr@mellanox.com \
--cc=gospo@cumulusnetworks.com \
--cc=idosch@mellanox.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=ogerlitz@mellanox.com \
--cc=rami.rosen@intel.com \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=yotamg@mellanox.com \
/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).