netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC v2 5/6] mlx4: report errors through extack
Date: Thu, 28 Feb 2019 19:07:30 -0800	[thread overview]
Message-ID: <20190228190716.4ef22216@cakuba.netronome.com> (raw)
In-Reply-To: <20190228215441.28275-6-stephen@networkplumber.org>

On Thu, 28 Feb 2019 13:54:40 -0800, Stephen Hemminger wrote:
> @@ -2870,8 +2873,8 @@ static int mlx4_xdp_set(struct net_device *dev, struct bpf_prog *prog)
>  	if (port_up) {
>  		err = mlx4_en_start_port(dev);
>  		if (err) {
> -			en_err(priv, "Failed starting port %d for XDP change\n",
> -			       priv->port);
> +			NL_SET_ERR_MSG_MOD(extack,
> +				       "Failed starting port for XDP change");

alignment is off now in a few spots

>  			queue_work(mdev->workqueue, &priv->watchdog_task);
>  		}
>  	}


  reply	other threads:[~2019-03-01  3:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 21:54 [RFC v2 0/6] use extack when setting up XDP Stephen Hemminger
2019-02-28 21:54 ` [RFC v2 1/6] bnxt: use extack for xdp error messages Stephen Hemminger
2019-02-28 21:54 ` [RFC v2 2/6] ixgbe: use extack for xdp errors Stephen Hemminger
2019-02-28 21:54 ` [RFC v2 3/6] i40e: use extack for bpf errors Stephen Hemminger
2019-03-01  3:06   ` Jakub Kicinski
2019-03-01 11:31     ` Maciej Fijalkowski
2019-03-01 16:28       ` Jakub Kicinski
2019-03-01 21:55         ` Stephen Hemminger
2019-03-01 22:03           ` Jakub Kicinski
2019-02-28 21:54 ` [RFC v2 4/6] ixgebvf: report xdp errors through extack Stephen Hemminger
2019-02-28 21:54 ` [RFC v2 5/6] mlx4: report " Stephen Hemminger
2019-03-01  3:07   ` Jakub Kicinski [this message]
2019-03-04 11:54   ` Tariq Toukan
2019-02-28 21:54 ` [RFC v2 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=20190228190716.4ef22216@cakuba.netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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).