From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, kuba@kernel.org, evgreen@chromium.org,
cpratapa@codeaurora.org, bjorn.andersson@linaro.org,
subashab@codeaurora.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/3] net: ipa: GSI interrupt handling fixes
Date: Wed, 23 Dec 2020 20:20:06 +0000 [thread overview]
Message-ID: <160875480654.17264.8645397184317449328.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201222180012.22489-1-elder@linaro.org>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Tue, 22 Dec 2020 12:00:09 -0600 you wrote:
> This series implements fixes for some issues related to handling
> interrupts when GSI channel and event ring commands complete.
>
> The first issue is that the completion condition for an event ring
> or channel command could occur while the associated interrupt is
> disabled. This would cause the interrupt to fire when it is
> subsequently enabled, even if the condition it signals had already
> been handled. The fix is to clear any pending interrupt conditions
> before re-enabling the interrupt.
>
> [...]
Here is the summary with links:
- [net,1/3] net: ipa: clear pending interrupts before enabling
https://git.kernel.org/netdev/net/c/94ad8f3ac6af
- [net,2/3] net: ipa: use state to determine channel command success
https://git.kernel.org/netdev/net/c/6ffddf3b3d18
- [net,3/3] net: ipa: use state to determine event ring command success
https://git.kernel.org/netdev/net/c/428b448ee764
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-12-23 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 18:00 [PATCH net 0/3] net: ipa: GSI interrupt handling fixes Alex Elder
2020-12-22 18:00 ` [PATCH net 1/3] net: ipa: clear pending interrupts before enabling Alex Elder
2020-12-22 18:00 ` [PATCH net 2/3] net: ipa: use state to determine channel command success Alex Elder
2020-12-26 18:51 ` kernel test robot
2020-12-22 18:00 ` [PATCH net 3/3] net: ipa: use state to determine event ring " Alex Elder
2020-12-23 20: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=160875480654.17264.8645397184317449328.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).