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: start using transaction IDs
Date: Mon, 05 Sep 2022 12:10:16 +0000 [thread overview]
Message-ID: <166237981638.17156.8447007118751978814.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220902210218.745873-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 2 Sep 2022 16:02:12 -0500 you wrote:
> A previous group of patches added ID fields to track the state of
> transactions:
> https://lore.kernel.org/netdev/20220831224017.377745-1-elder@linaro.org
>
> This series starts using those IDs instead of the lists used
> previously. Most of this series involves reworking the function
> that determines which transaction is the "last", which determines
> when a channel has been quiesed. The last patch is mainly used to
> prove that the new index method of tracking transaction state is
> equivalent to the previous use of lists.
>
> [...]
Here is the summary with links:
- [net-next,1/6] net: ipa: rework last transaction determination
https://git.kernel.org/netdev/net-next/c/b2abe33d23cf
- [net-next,2/6] net: ipa: use IDs for last allocated transaction
https://git.kernel.org/netdev/net-next/c/c30623ea0b3a
- [net-next,3/6] net: ipa: use IDs exclusively for last transaction
https://git.kernel.org/netdev/net-next/c/897c0ce665d6
- [net-next,4/6] net: ipa: simplify gsi_channel_trans_last()
https://git.kernel.org/netdev/net-next/c/e68d1d1591fd
- [net-next,5/6] net: ipa: further simplify gsi_channel_trans_last()
https://git.kernel.org/netdev/net-next/c/4601e75596cb
- [net-next,6/6] net: ipa: verify a few more IDs
https://git.kernel.org/netdev/net-next/c/8672bab7eb94
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-05 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 21:02 [PATCH net-next 0/6] net: ipa: start using transaction IDs Alex Elder
2022-09-02 21:02 ` [PATCH net-next 1/6] net: ipa: rework last transaction determination Alex Elder
2022-09-02 21:02 ` [PATCH net-next 2/6] net: ipa: use IDs for last allocated transaction Alex Elder
2022-09-02 21:02 ` [PATCH net-next 3/6] net: ipa: use IDs exclusively for last transaction Alex Elder
2022-09-02 21:02 ` [PATCH net-next 4/6] net: ipa: simplify gsi_channel_trans_last() Alex Elder
2022-09-02 21:02 ` [PATCH net-next 5/6] net: ipa: further " Alex Elder
2022-09-02 21:02 ` [PATCH net-next 6/6] net: ipa: verify a few more IDs Alex Elder
2022-09-05 12:10 ` 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=166237981638.17156.8447007118751978814.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