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 v2 0/5] net: ipa: small transaction updates
Date: Thu, 21 Jul 2022 04:10:17 +0000 [thread overview]
Message-ID: <165837661742.25559.4645505157556019794.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220719181020.372697-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 19 Jul 2022 13:10:15 -0500 you wrote:
> Version 2 of this series corrects a misspelling of "outstanding"
> pointed out by the netdev test bots. (For some reason I don't see
> that when I run "checkpatch".) I found and fixed a second instance
> of that word being misspelled as well.
>
> This series includes three changes to the transaction code. The
> first adds a new transaction list that represents a distinct state
> that has not been maintained. The second moves a field in the
> transaction information structure, and reorders its initialization
> a bit. The third skips a function call when it is known not to be
> necessary.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/5] net: ipa: add a transaction committed list
https://git.kernel.org/netdev/net-next/c/b63f507c06e6
- [net-next,v2,2/5] net: ipa: rearrange transaction initialization
(no matching commit)
- [net-next,v2,3/5] net: ipa: skip some cleanup for unused transactions
https://git.kernel.org/netdev/net-next/c/4d8996cbeeab
- [net-next,v2,4/5] net: ipa: report when the driver has been removed
https://git.kernel.org/netdev/net-next/c/3c91c86d1bb6
- [net-next,v2,5/5] net: ipa: fix an outdated comment
https://git.kernel.org/netdev/net-next/c/616c4a83b6ea
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-07-21 4:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 18:10 [PATCH net-next v2 0/5] net: ipa: small transaction updates Alex Elder
2022-07-19 18:10 ` [PATCH net-next v2 1/5] net: ipa: add a transaction committed list Alex Elder
2022-07-19 18:10 ` [PATCH net-next v2 2/5] net: ipa: rearrange transaction initialization Alex Elder
2022-07-19 18:10 ` [PATCH net-next v2 3/5] net: ipa: skip some cleanup for unused transactions Alex Elder
2022-07-19 18:10 ` [PATCH net-next v2 4/5] net: ipa: report when the driver has been removed Alex Elder
2022-07-19 18:10 ` [PATCH net-next v2 5/5] net: ipa: fix an outdated comment Alex Elder
2022-07-21 4: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=165837661742.25559.4645505157556019794.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).