From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, kuba@kernel.org, evgreen@chromium.org,
subashab@codeaurora.org, cpratapa@codeaurora.org,
bjorn.andersson@linaro.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/6] net: ipa: add a driver shutdown callback
Date: Sat, 21 Nov 2020 03:00:07 +0000 [thread overview]
Message-ID: <160592760704.22843.591870279571575772.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201119224929.23819-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 19 Nov 2020 16:49:23 -0600 you wrote:
> The final patch in this series adds a driver shutdown callback for
> the IPA driver. The patches leading up to that address some issues
> encountered while ensuring that callback worked as expected:
> - The first just reports a little more information when channels
> or event rings are in unexpected states
> - The second patch recognizes a condition where an as-yet-unused
> channel does not require a reset during teardown
> - The third patch explicitly ignores a certain error condition,
> because it can't be avoided, and is harmless if it occurs
> - The fourth properly handles requests to retry a channel HALT
> request
> - The fifth makes a second attempt to stop modem activity during
> shutdown if it's busy
>
> [...]
Here is the summary with links:
- [net-next,1/6] net: ipa: print channel/event ring number on error
https://git.kernel.org/netdev/net-next/c/f8d3bdd561a7
- [net-next,2/6] net: ipa: don't reset an ALLOCATED channel
https://git.kernel.org/netdev/net-next/c/5d28913d4ee6
- [net-next,3/6] net: ipa: ignore CHANNEL_NOT_RUNNING errors
https://git.kernel.org/netdev/net-next/c/f849afcc8c3b
- [net-next,4/6] net: ipa: support retries on generic GSI commands
https://git.kernel.org/netdev/net-next/c/1136145660f3
- [net-next,5/6] net: ipa: retry modem stop if busy
https://git.kernel.org/netdev/net-next/c/7c80e83829db
- [net-next,6/6] net: ipa: add driver shutdown callback
https://git.kernel.org/netdev/net-next/c/ae1d72f9779f
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:[~2020-11-21 3:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 22:49 [PATCH net-next 0/6] net: ipa: add a driver shutdown callback Alex Elder
2020-11-19 22:49 ` [PATCH net-next 1/6] net: ipa: print channel/event ring number on error Alex Elder
2020-11-19 22:49 ` [PATCH net-next 2/6] net: ipa: don't reset an ALLOCATED channel Alex Elder
2020-11-19 22:49 ` [PATCH net-next 3/6] net: ipa: ignore CHANNEL_NOT_RUNNING errors Alex Elder
2020-11-19 22:49 ` [PATCH net-next 4/6] net: ipa: support retries on generic GSI commands Alex Elder
2020-11-21 2:49 ` Jakub Kicinski
2020-11-21 3:31 ` Alex Elder
2020-11-21 3:46 ` Jakub Kicinski
2020-11-19 22:49 ` [PATCH net-next 5/6] net: ipa: retry modem stop if busy Alex Elder
2020-11-19 22:49 ` [PATCH net-next 6/6] net: ipa: add driver shutdown callback Alex Elder
2020-11-21 3:00 ` 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=160592760704.22843.591870279571575772.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=subashab@codeaurora.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).