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,
andersson@kernel.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: a mix of cleanups
Date: Tue, 20 Sep 2022 14:50:17 +0000 [thread overview]
Message-ID: <166368541731.14330.5858659115387897586.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220910011131.1431934-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 9 Sep 2022 20:11:25 -0500 you wrote:
> This series contains a set of cleanups done in preparation for a
> more substantitive upcoming series that reworks how IPA registers
> and their fields are defined.
>
> The first eliminates about half of the possible GSI register
> constant symbols by removing offset definitions that are not
> currently required.
>
> [...]
Here is the summary with links:
- [net-next,1/6] net: ipa: don't define unneeded GSI register offsets
https://git.kernel.org/netdev/net-next/c/5ea4285829de
- [net-next,2/6] net: ipa: move the definition of gsi_ee_id
https://git.kernel.org/netdev/net-next/c/bb788de30a74
- [net-next,3/6] net: ipa: move and redefine ipa_version_valid()
https://git.kernel.org/netdev/net-next/c/8b3cb084b23e
- [net-next,4/6] net: ipa: don't reuse variable names
https://git.kernel.org/netdev/net-next/c/9eefd2fb966d
- [net-next,5/6] net: ipa: update sequencer definition constraints
https://git.kernel.org/netdev/net-next/c/a14d593724c4
- [net-next,6/6] net: ipa: fix two symbol names
https://git.kernel.org/netdev/net-next/c/dae4af6bf232
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-20 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 1:11 [PATCH net-next 0/6] net: ipa: a mix of cleanups Alex Elder
2022-09-10 1:11 ` [PATCH net-next 1/6] net: ipa: don't define unneeded GSI register offsets Alex Elder
2022-09-10 1:11 ` [PATCH net-next 2/6] net: ipa: move the definition of gsi_ee_id Alex Elder
2022-09-10 1:11 ` [PATCH net-next 3/6] net: ipa: move and redefine ipa_version_valid() Alex Elder
2022-09-20 8:29 ` Paolo Abeni
2022-09-20 12:50 ` Alex Elder
2022-09-20 13:37 ` Paolo Abeni
2022-09-10 1:11 ` [PATCH net-next 4/6] net: ipa: don't reuse variable names Alex Elder
2022-09-10 1:11 ` [PATCH net-next 5/6] net: ipa: update sequencer definition constraints Alex Elder
2022-09-10 1:11 ` [PATCH net-next 6/6] net: ipa: fix two symbol names Alex Elder
2022-09-20 14: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=166368541731.14330.5858659115387897586.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andersson@kernel.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