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: don't use lists for transaction state
Date: Fri, 09 Sep 2022 10:50:17 +0000 [thread overview]
Message-ID: <166272061793.26556.14430225024454087661.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220906171942.957704-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 6 Sep 2022 12:19:37 -0500 you wrote:
> This is the last series of patches to convert the IPA code so
> integer IDs are used rather than lists to track the state of
> transactions.
>
> A first series of patches added ID fields to track the state of
> transactions:
> https://lore.kernel.org/netdev/20220831224017.377745-1-elder@linaro.org
> The second series started transitioning code to use these IDs rather
> than lists to manage state:
> https://lore.kernel.org/netdev/20220902210218.745873-1-elder@linaro.org
>
> [...]
Here is the summary with links:
- [net-next,1/5] net: ipa: always use transaction IDs instead of lists
(no matching commit)
- [net-next,2/5] net: ipa: kill the allocated transaction list
https://git.kernel.org/netdev/net-next/c/11902b41f2fa
- [net-next,3/5] net: ipa: kill all other transaction lists
https://git.kernel.org/netdev/net-next/c/d338ae28d8a8
- [net-next,4/5] net: ipa: update channel in gsi_channel_trans_complete()
https://git.kernel.org/netdev/net-next/c/e0e3406c60d7
- [net-next,5/5] net: ipa: don't have gsi_channel_update() return a value
https://git.kernel.org/netdev/net-next/c/019e37eaef97
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-09 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 17:19 [PATCH net-next 0/6] net: ipa: don't use lists for transaction state Alex Elder
2022-09-06 17:19 ` [PATCH net-next 1/5] net: ipa: always use transaction IDs instead of lists Alex Elder
2022-09-06 17:19 ` [PATCH net-next 2/5] net: ipa: kill the allocated transaction list Alex Elder
2022-09-06 17:19 ` [PATCH net-next 3/5] net: ipa: kill all other transaction lists Alex Elder
2022-09-06 17:19 ` [PATCH net-next 4/5] net: ipa: update channel in gsi_channel_trans_complete() Alex Elder
2022-09-06 17:19 ` [PATCH net-next 5/5] net: ipa: don't have gsi_channel_update() return a value Alex Elder
2022-09-09 10:50 ` 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=166272061793.26556.14430225024454087661.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