From: dsahern@kernel.org
To: netdev@vger.kernel.org
Cc: idosch@mellanox.com, jiri@mellanox.com,
jakub.kicinski@netronome.com, David Ahern <dsahern@gmail.com>
Subject: [PATCH v2 net-next 0/3] devlink: Add extack messages for reload and port split/unsplit
Date: Tue, 5 Jun 2018 08:14:08 -0700 [thread overview]
Message-ID: <20180605151411.20310-1-dsahern@kernel.org> (raw)
From: David Ahern <dsahern@gmail.com>
Patch 1 adds extack arg to reload, port_split and port_unsplit devlink
operations.
Patch 2 adds extack messages for reload operation in netdevsim.
Patch 3 adds extack messages to port split/unsplit in mlxsw driver.
v2
- make the extack messages align with existing dev_err
David Ahern (3):
devlink: Add extack to reload and port_{un,}split operations
netdevsim: Add extack error message for devlink reload
mlxsw: Add extack messages for port_{un,}split failures
drivers/net/ethernet/mellanox/mlxsw/core.c | 23 ++++++++++++++++-------
drivers/net/ethernet/mellanox/mlxsw/core.h | 5 +++--
drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 15 ++++++++++++---
drivers/net/ethernet/netronome/nfp/nfp_devlink.c | 5 +++--
drivers/net/netdevsim/devlink.c | 7 ++++---
drivers/net/netdevsim/fib.c | 9 ++++++---
drivers/net/netdevsim/netdevsim.h | 3 ++-
include/net/devlink.h | 7 ++++---
net/core/devlink.c | 18 ++++++++++--------
9 files changed, 60 insertions(+), 32 deletions(-)
--
2.11.0
next reply other threads:[~2018-06-05 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 15:14 dsahern [this message]
2018-06-05 15:14 ` [PATCH v2 net-next 1/3] devlink: Add extack to reload and port_{un,}split operations dsahern
2018-06-05 15:14 ` [PATCH v2 net-next 2/3] netdevsim: Add extack error message for devlink reload dsahern
2018-06-05 15:14 ` [PATCH v2 net-next 3/3] mlxsw: Add extack messages for port_{un,}split failures dsahern
2018-06-05 15:15 ` Jiri Pirko
2018-06-05 16:32 ` [PATCH v2 net-next 0/3] devlink: Add extack messages for reload and port split/unsplit 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=20180605151411.20310-1-dsahern@kernel.org \
--to=dsahern@kernel.org \
--cc=dsahern@gmail.com \
--cc=idosch@mellanox.com \
--cc=jakub.kicinski@netronome.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).