From: Ido Schimmel <idosch@idosch.org>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, jiri@nvidia.com,
mlxsw@nvidia.com, Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net 0/2] mlxsw: Couple of fixes
Date: Tue, 17 Nov 2020 19:33:50 +0200 [thread overview]
Message-ID: <20201117173352.288491-1-idosch@idosch.org> (raw)
From: Ido Schimmel <idosch@nvidia.com>
This patch set contains two fixes for mlxsw.
Patch #1 fixes firmware flashing when CONFIG_MLXSW_CORE=y and
CONFIG_MLXFW=m.
Patch #2 prevents EMAD transactions from needlessly failing when the
system is under heavy load by using exponential backoff.
Please consider patch #2 for stable.
Ido Schimmel (2):
mlxsw: Fix firmware flashing
mlxsw: core: Use variable timeout for EMAD retries
drivers/net/ethernet/mellanox/mlxsw/Kconfig | 2 +-
drivers/net/ethernet/mellanox/mlxsw/core.c | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
--
2.28.0
next reply other threads:[~2020-11-17 17:35 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 17:33 Ido Schimmel [this message]
2020-11-17 17:33 ` [PATCH net 1/2] mlxsw: Fix firmware flashing Ido Schimmel
2020-11-17 17:33 ` [PATCH net 2/2] mlxsw: core: Use variable timeout for EMAD retries Ido Schimmel
2020-11-18 19:09 ` [PATCH net 0/2] mlxsw: Couple of fixes Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2019-12-29 11:40 Ido Schimmel
2019-12-29 20:30 ` David Miller
2018-10-29 14:26 Ido Schimmel
2018-10-30 3:48 ` David Miller
2018-10-04 15:48 Ido Schimmel
2018-10-04 16:56 ` David Miller
2018-10-04 17:05 ` Ido Schimmel
2018-02-27 11:56 [patch net 0/2] mlxsw: couple " Jiri Pirko
2018-02-27 19:39 ` David Miller
2018-02-28 7:09 ` Jiri Pirko
2018-01-10 10:42 Jiri Pirko
2018-01-10 20:58 ` David Miller
2017-08-04 12:12 [patch net 0/2] mlxsw: Couple " Jiri Pirko
2017-08-04 18:17 ` David Miller
2017-05-18 7:18 [patch net 0/2] mlxsw: couple " Jiri Pirko
2017-05-18 15:05 ` David Miller
2017-03-14 12:59 [patch net 0/2] mlxsw: Couple " Jiri Pirko
2017-03-14 18:35 ` David Miller
2016-11-11 10:20 Jiri Pirko
2016-11-13 17:48 ` David Miller
2016-10-25 9:25 Jiri Pirko
2016-10-28 17:44 ` David Miller
2016-10-04 7:46 Jiri Pirko
2016-10-05 0:29 ` David Miller
2016-10-05 11:14 ` Jiri Pirko
2016-09-08 6:16 [patch net 0/2] mlxsw: couple " Jiri Pirko
2016-09-09 23:57 ` David Miller
2016-08-24 9:18 Jiri Pirko
2016-08-24 16:39 ` David Miller
2016-06-17 13:09 Jiri Pirko
2016-06-18 4:58 ` David Miller
2016-06-09 7:51 Jiri Pirko
2016-06-09 18:21 ` David Miller
2016-05-06 20:18 [patch net 0/2] mlxsw: Couple " Jiri Pirko
2016-05-06 22:33 ` David Miller
2016-03-07 8:24 [patch net 0/2] mlxsw: couple " Jiri Pirko
2015-10-08 13:17 Jiri Pirko
2015-10-11 12:08 ` 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=20201117173352.288491-1-idosch@idosch.org \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.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).