From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, idosch@nvidia.com,
amitc@mellanox.com, mlxsw@nvidia.com
Subject: Re: [PATCH net] mlxsw: pci: Fix possible crash during initialization
Date: Wed, 19 Apr 2023 12:10:20 +0000 [thread overview]
Message-ID: <168190622025.8890.5823614081879485303.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <303aa6102f0f9a8be9af749342d2afc82dd9dc53.1681749167.git.petrm@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 17 Apr 2023 18:52:51 +0200 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> During initialization the driver issues a reset command via its command
> interface in order to remove previous configuration from the device.
>
> After issuing the reset, the driver waits for 200ms before polling on
> the "system_status" register using memory-mapped IO until the device
> reaches a ready state (0x5E). The wait is necessary because the reset
> command only triggers the reset, but the reset itself happens
> asynchronously. If the driver starts polling too soon, the read of the
> "system_status" register will never return and the system will crash
> [1].
>
> [...]
Here is the summary with links:
- [net] mlxsw: pci: Fix possible crash during initialization
https://git.kernel.org/netdev/net/c/1f64757ee2bb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-04-19 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 16:52 [PATCH net] mlxsw: pci: Fix possible crash during initialization Petr Machata
2023-04-19 12:10 ` patchwork-bot+netdevbpf [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=168190622025.8890.5823614081879485303.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amitc@mellanox.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.