[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190524085446.59dc6f2f@cakuba.netronome.com>
Date: Fri, 24 May 2019 08:54:46 -0700
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: David Ahern <dsahern@...il.com>, netdev@...r.kernel.org,
davem@...emloft.net, mlxsw@...lanox.com, sthemmin@...rosoft.com,
saeedm@...lanox.com, leon@...nel.org
Subject: Re: [patch net-next 3/7] mlxfw: Propagate error messages through
extack
On Fri, 24 May 2019 10:11:10 +0200, Jiri Pirko wrote:
> Thu, May 23, 2019 at 05:19:46PM CEST, dsahern@...il.com wrote:
> >On 5/23/19 3:45 AM, Jiri Pirko wrote:
> >> @@ -57,11 +58,13 @@ static int mlxfw_fsm_state_wait(struct mlxfw_dev *mlxfw_dev, u32 fwhandle,
> >> if (fsm_state_err != MLXFW_FSM_STATE_ERR_OK) {
> >> pr_err("Firmware flash failed: %s\n",
> >> mlxfw_fsm_state_err_str[fsm_state_err]);
> >> + NL_SET_ERR_MSG_MOD(extack, "Firmware flash failed");
> >> return -EINVAL;
> >> }
> >> if (curr_fsm_state != fsm_state) {
> >> if (--times == 0) {
> >> pr_err("Timeout reached on FSM state change");
> >> + NL_SET_ERR_MSG_MOD(extack, "Timeout reached on FSM state change");
> >
> >FSM? Is the meaning obvious to users?
>
> It is specific to mlx drivers.
What does it stand for? Isn't it just Finite State Machine?
Powered by blists - more mailing lists