[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191112.105421.1175237105425742696.davem@davemloft.net>
Date: Tue, 12 Nov 2019 10:54:21 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: idosch@...sch.org
Cc: netdev@...r.kernel.org, jiri@...lanox.com, shalomt@...lanox.com,
jakub.kicinski@...ronome.com, mlxsw@...lanox.com,
idosch@...lanox.com
Subject: Re: [PATCH net-next v2 0/7] mlxsw: Add extended ACK for EMADs
From: Ido Schimmel <idosch@...sch.org>
Date: Tue, 12 Nov 2019 08:48:23 +0200
> From: Ido Schimmel <idosch@...lanox.com>
>
> Shalom says:
>
> Ethernet Management Datagrams (EMADs) are Ethernet packets sent between
> the driver and device's firmware. They are used to pass various
> configurations to the device, but also to get events (e.g., port up)
> from it. After the Ethernet header, these packets are built in a TLV
> format.
>
> Up until now, whenever the driver issued an erroneous register access it
> only got an error code indicating a bad parameter was used. This patch
> set adds a new TLV (string TLV) that can be used by the firmware to
> encode a 128 character string describing the error. The new TLV is
> allocated by the driver and set to zeros. In case of error, the driver
> will check the length of the string in the response and report it using
> devlink hwerr tracepoint.
...
Series applied, thank you.
Powered by blists - more mailing lists