From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org,
vitaly.lifshits@intel.com, regressions@leemhuis.info,
stable@vger.kernel.org, cJ@zougloub.eu, sasha.neftin@intel.com,
dima.ruinskiy@intel.com
Subject: Re: [PATCH net] e1000e: change usleep_range to udelay in PHY mdic access
Date: Wed, 01 May 2024 01:50:29 +0000 [thread overview]
Message-ID: <171452822939.22205.9211617153517176455.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240429171040.1152516-1-anthony.l.nguyen@intel.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 29 Apr 2024 10:10:40 -0700 you wrote:
> From: Vitaly Lifshits <vitaly.lifshits@intel.com>
>
> This is a partial revert of commit 6dbdd4de0362 ("e1000e: Workaround
> for sporadic MDI error on Meteor Lake systems"). The referenced commit
> used usleep_range inside the PHY access routines, which are sometimes
> called from an atomic context. This can lead to a kernel panic in some
> scenarios, such as cable disconnection and reconnection on vPro systems.
>
> [...]
Here is the summary with links:
- [net] e1000e: change usleep_range to udelay in PHY mdic access
https://git.kernel.org/netdev/net/c/387f295cb215
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:[~2024-05-01 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 17:10 [PATCH net] e1000e: change usleep_range to udelay in PHY mdic access Tony Nguyen
2024-04-30 17:31 ` Simon Horman
2024-05-01 1:50 ` 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=171452822939.22205.9211617153517176455.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=cJ@zougloub.eu \
--cc=davem@davemloft.net \
--cc=dima.ruinskiy@intel.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@leemhuis.info \
--cc=sasha.neftin@intel.com \
--cc=stable@vger.kernel.org \
--cc=vitaly.lifshits@intel.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 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).