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: simplify completion statistics
Date: Wed, 15 Jun 2022 08:20:14 +0000 [thread overview]
Message-ID: <165528121475.11773.6004153793854654666.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220613171759.578856-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 13 Jun 2022 12:17:53 -0500 you wrote:
> The first patch in this series makes the name used for variables
> representing a TRE ring be consistent everywhere. The second
> renames two structure fields to better represent their purpose.
>
> The last four rework a little code that manages some tranaction and
> byte transfer statistics maintained mainly for TX endpoints. For
> the most part this series is refactoring. The last one also
> includes the first step toward no longer assuming an event ring is
> dedicated to a single channel.
>
> [...]
Here is the summary with links:
- [net-next,1/6] net: ipa: use "tre_ring" for all TRE ring local variables
https://git.kernel.org/netdev/net-next/c/2295947bdaa6
- [net-next,2/6] net: ipa: rename two transaction fields
https://git.kernel.org/netdev/net-next/c/3eeabea6c895
- [net-next,3/6] net: ipa: introduce gsi_trans_tx_committed()
https://git.kernel.org/netdev/net-next/c/4e0f28e9ee4b
- [net-next,4/6] net: ipa: simplify TX completion statistics
https://git.kernel.org/netdev/net-next/c/65d39497fab6
- [net-next,5/6] net: ipa: stop counting total RX bytes and transactions
https://git.kernel.org/netdev/net-next/c/dbad2fa71914
- [net-next,6/6] net: ipa: rework gsi_channel_tx_update()
(no matching commit)
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-06-15 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 17:17 [PATCH net-next 0/6] net: ipa: simplify completion statistics Alex Elder
2022-06-13 17:17 ` [PATCH net-next 1/6] net: ipa: use "tre_ring" for all TRE ring local variables Alex Elder
2022-06-13 17:17 ` [PATCH net-next 2/6] net: ipa: rename two transaction fields Alex Elder
2022-06-13 17:17 ` [PATCH net-next 3/6] net: ipa: introduce gsi_trans_tx_committed() Alex Elder
2022-06-13 17:17 ` [PATCH net-next 4/6] net: ipa: simplify TX completion statistics Alex Elder
2022-06-13 17:17 ` [PATCH net-next 5/6] net: ipa: stop counting total RX bytes and transactions Alex Elder
2022-06-13 17:17 ` [PATCH net-next 6/6] net: ipa: rework gsi_channel_tx_update() Alex Elder
2022-06-15 8: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=165528121475.11773.6004153793854654666.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