From: patchwork-bot+netdevbpf@kernel.org
To: AceLan Kao <acelan.kao@canonical.com>
Cc: irusskikh@marvell.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, labre@posteo.de,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] net: atlantic: remove deep parameter on suspend/resume functions
Date: Thu, 14 Jul 2022 12:40:13 +0000 [thread overview]
Message-ID: <165780241363.16224.10800980406079530164.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220713111224.1535938-1-acelan.kao@canonical.com>
Hello:
This series was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 13 Jul 2022 19:12:23 +0800 you wrote:
> From: "Chia-Lin Kao (AceLan)" <acelan.kao@canonical.com>
>
> Below commit claims that atlantic NIC requires to reset the device on pm
> op, and had set the deep to true for all suspend/resume functions.
> commit 1809c30b6e5a ("net: atlantic: always deep reset on pm op, fixing up my null deref regression")
> So, we could remove deep parameter on suspend/resume functions without
> any functional change.
>
> [...]
Here is the summary with links:
- [1/2] net: atlantic: remove deep parameter on suspend/resume functions
https://git.kernel.org/netdev/net/c/0f3325076038
- [2/2] net: atlantic: remove aq_nic_deinit() when resume
https://git.kernel.org/netdev/net/c/2e15c51fefaf
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:[~2022-07-14 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 11:12 [PATCH 1/2] net: atlantic: remove deep parameter on suspend/resume functions AceLan Kao
2022-07-13 11:12 ` [PATCH 2/2] net: atlantic: remove aq_nic_deinit() when resume AceLan Kao
2022-07-14 12:40 ` 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=165780241363.16224.10800980406079530164.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acelan.kao@canonical.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=labre@posteo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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