public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
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, sasha.neftin@intel•com,
	hui.wang@canonical•com, pmenzel@molgen•mpg.de,
	todd.e.brandt@intel•com, dmummenschanz@web•de,
	morx.bar.gabay@intel•com
Subject: Re: [PATCH net] e1000e: fix force smbus during suspend flow
Date: Thu, 11 Jul 2024 02:20:30 +0000	[thread overview]
Message-ID: <172066443066.28307.16973037048881070755.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240709203123.2103296-1-anthony.l.nguyen@intel.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:

On Tue,  9 Jul 2024 13:31:22 -0700 you wrote:
> From: Vitaly Lifshits <vitaly.lifshits@intel•com>
> 
> Commit 861e8086029e ("e1000e: move force SMBUS from enable ulp function
> to avoid PHY loss issue") resolved a PHY access loss during suspend on
> Meteor Lake consumer platforms, but it affected corporate systems
> incorrectly.
> 
> [...]

Here is the summary with links:
  - [net] e1000e: fix force smbus during suspend flow
    https://git.kernel.org/netdev/net/c/76a0a3f9cc2f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-07-11  2:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 20:31 [PATCH net] e1000e: fix force smbus during suspend flow Tony Nguyen
2024-07-10 10:20 ` Simon Horman
2024-07-11  2:20 ` 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=172066443066.28307.16973037048881070755.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=anthony.l.nguyen@intel$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=dmummenschanz@web$(echo .)de \
    --cc=edumazet@google$(echo .)com \
    --cc=hui.wang@canonical$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=morx.bar.gabay@intel$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=pmenzel@molgen$(echo .)mpg.de \
    --cc=sasha.neftin@intel$(echo .)com \
    --cc=todd.e.brandt@intel$(echo .)com \
    --cc=vitaly.lifshits@intel$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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