From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mka@chromium.org, evgreen@chromium.org,
bjorn.andersson@linaro.org, quic_cpratapa@quicinc.com,
quic_avuyyuru@quicinc.com, quic_jponduru@quicinc.com,
quic_subashab@quicinc.com, elder@kernel.org,
netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/6] net: ipa: use IDs to track transaction state
Date: Fri, 02 Sep 2022 11:30:17 +0000 [thread overview]
Message-ID: <166211821777.29115.5588215360001640373.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220831224017.377745-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 31 Aug 2022 17:40:11 -0500 you wrote:
> This series is the first of three groups of changes that simplify
> the way the IPA driver tracks the state of its transactions.
>
> Each GSI channel has a fixed number of transactions allocated at
> initialization time. The number allocated matches the number of
> TREs in the transfer ring associated with the channel. This is
> because the transfer ring limits the number of transfers that can
> ever be underway, and in the worst case, each transaction represents
> a single TRE.
>
> [...]
Here is the summary with links:
- [net-next,1/6] net: ipa: use an array for transactions
(no matching commit)
- [net-next,2/6] net: ipa: track allocated transactions with an ID
https://git.kernel.org/netdev/net-next/c/41e2a2c054b8
- [net-next,3/6] net: ipa: track committed transactions with an ID
https://git.kernel.org/netdev/net-next/c/fc95d958e27d
- [net-next,4/6] net: ipa: track pending transactions with an ID
https://git.kernel.org/netdev/net-next/c/eeff7c14e08c
- [net-next,5/6] net: ipa: track completed transactions with an ID
https://git.kernel.org/netdev/net-next/c/949cd0b5c296
- [net-next,6/6] net: ipa: track polled transactions with an ID
https://git.kernel.org/netdev/net-next/c/fd3bd0398a0d
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-09-02 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 22:40 [PATCH net-next 0/6] net: ipa: use IDs to track transaction state Alex Elder
2022-08-31 22:40 ` [PATCH net-next 1/6] net: ipa: use an array for transactions Alex Elder
2022-08-31 22:40 ` [PATCH net-next 2/6] net: ipa: track allocated transactions with an ID Alex Elder
2022-08-31 22:40 ` [PATCH net-next 3/6] net: ipa: track committed " Alex Elder
2022-08-31 22:40 ` [PATCH net-next 4/6] net: ipa: track pending " Alex Elder
2022-08-31 22:40 ` [PATCH net-next 5/6] net: ipa: track completed " Alex Elder
2022-08-31 22:40 ` [PATCH net-next 6/6] net: ipa: track polled " Alex Elder
2022-09-02 11:30 ` 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=166211821777.29115.5588215360001640373.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_avuyyuru@quicinc.com \
--cc=quic_cpratapa@quicinc.com \
--cc=quic_jponduru@quicinc.com \
--cc=quic_subashab@quicinc.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).