From: David Miller <davem@davemloft.net>
To: idosch@mellanox.com
Cc: netdev@vger.kernel.org, jiri@mellanox.com, mlxsw@mellanox.com
Subject: Re: [PATCH net-next 0/3] mlxsw: use MRSR register for FW reset
Date: Tue, 29 May 2018 10:10:24 -0400 (EDT) [thread overview]
Message-ID: <20180529.101024.1307604490593495020.davem@davemloft.net> (raw)
In-Reply-To: <20180527065615.1329-1-idosch@mellanox.com>
From: Ido Schimmel <idosch@mellanox.com>
Date: Sun, 27 May 2018 09:56:12 +0300
> Jiri says:
>
> Introduce a MRSR register definition and use it to do FW reset instead
> of existing mechanism using PCI BAR0 register.
Series applied to net-next.
prev parent reply other threads:[~2018-05-29 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 6:56 [PATCH net-next 0/3] mlxsw: use MRSR register for FW reset Ido Schimmel
2018-05-27 6:56 ` [PATCH net-next 1/3] mlxsw: reg: Add Management Reset and Shutdown Register Ido Schimmel
2018-05-27 6:56 ` [PATCH net-next 2/3] mlxsw: cmd: Handle error after reset gracefully Ido Schimmel
2018-05-27 6:56 ` [PATCH net-next 3/3] mlxsw: pci: Utilize MRSR register to perform FW reset Ido Schimmel
2018-05-29 14:10 ` David Miller [this message]
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=20180529.101024.1307604490593495020.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.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).