From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Cc: Stephen Hemminger <sthemmin@microsoft.com>
Subject: [RFC 0/7] ndo_bpf error reporting
Date: Thu, 28 Feb 2019 10:38:03 -0800 [thread overview]
Message-ID: <20190228183809.25417-1-sthemmin@microsoft.com> (raw)
Several drivers are logging errors to console rather than
using xdp->extack to report problems. Try and make user
experience consistent.
Note: these patches are RFC because compile tested only.
Stephen Hemminger (6):
bnxt: use extack for xdp error messages
ixgbe: use extack for xdp errors
i40e: use extack for bpf errors
ixgebvf: report xdp errors through extack
mlx4: report errors through extack
mlx5: report XDP errors through extack
drivers/net/ethernet/broadcom/bnxt/bnxt_xdp.c | 26 +++++++++----------
drivers/net/ethernet/intel/i40e/i40e_main.c | 14 +++++++---
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 25 +++++++++++++-----
.../net/ethernet/intel/ixgbevf/ixgbevf_main.c | 11 +++++---
.../net/ethernet/mellanox/mlx4/en_netdev.c | 14 ++++++----
.../net/ethernet/mellanox/mlx5/core/en_main.c | 22 +++++++++-------
6 files changed, 71 insertions(+), 41 deletions(-)
--
2.17.1
next reply other threads:[~2019-02-28 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 18:38 Stephen Hemminger [this message]
2019-02-28 18:38 ` [RFC 1/6] bnxt: use extack for xdp error messages Stephen Hemminger
2019-02-28 18:43 ` Jakub Kicinski
2019-02-28 18:38 ` [RFC 2/6] ixgbe: use extack for xdp errors Stephen Hemminger
2019-02-28 19:04 ` Dan Williams
2019-02-28 18:38 ` [RFC 3/6] i40e: use extack for bpf errors Stephen Hemminger
2019-02-28 18:38 ` [RFC 4/6] ixgebvf: report xdp errors through extack Stephen Hemminger
2019-02-28 18:38 ` [RFC 5/6] mlx4: report " Stephen Hemminger
2019-02-28 18:38 ` [RFC 6/6] mlx5: report XDP " 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=20190228183809.25417-1-sthemmin@microsoft.com \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.