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, caleb.connolly@linaro.org, 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/9] net: ipa: prepare for GSI register updtaes
Date: Fri, 10 Feb 2023 08:50:19 +0000 [thread overview]
Message-ID: <167601901934.32230.173851279004955737.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230208205653.177700-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 8 Feb 2023 14:56:44 -0600 you wrote:
> An upcoming series (or two) will convert the definitions of GSI
> registers used by IPA so they use the "IPA reg" mechanism to specify
> register offsets and their fields. This will simplify implementing
> the fairly large number of changes required in GSI registers to
> support more than 32 GSI channels (introduced in IPA v5.0).
>
> A few minor problems and inconsistencies were found, and they're
> fixed here. The last three patches in this series change the
> "ipa_reg" code to separate the IPA-specific part (the base virtual
> address, basically) from the generic register part, and the now-
> generic code is renamed to use just "reg_" or "REG_" as a prefix
> rather than "ipa_reg" or "IPA_REG_".
>
> [...]
Here is the summary with links:
- [net-next,1/9] net: ipa: generic command param fix
https://git.kernel.org/netdev/net-next/c/2df181f09c96
- [net-next,2/9] net: ipa: get rid of ipa->reg_addr
https://git.kernel.org/netdev/net-next/c/38028e6f3923
- [net-next,3/9] net: ipa: add some new IPA versions
https://git.kernel.org/netdev/net-next/c/3aac8ec1c028
- [net-next,4/9] net: ipa: tighten up IPA register validity checking
https://git.kernel.org/netdev/net-next/c/d86603e940ae
- [net-next,5/9] net: ipa: use bitmasks for GSI IRQ values
https://git.kernel.org/netdev/net-next/c/c5ebba75c762
- [net-next,6/9] net: ipa: GSI register cleanup
https://git.kernel.org/netdev/net-next/c/0ec573ef2a1b
- [net-next,7/9] net: ipa: start generalizing "ipa_reg"
(no matching commit)
- [net-next,8/9] net: ipa: generalize register offset functions
https://git.kernel.org/netdev/net-next/c/fc4cecf70675
- [net-next,9/9] net: ipa: generalize register field functions
https://git.kernel.org/netdev/net-next/c/f1470fd790b0
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:[~2023-02-10 8:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 20:56 [PATCH net-next 0/9] net: ipa: prepare for GSI register updtaes Alex Elder
2023-02-08 20:56 ` [PATCH net-next 1/9] net: ipa: generic command param fix Alex Elder
2023-02-08 20:56 ` [PATCH net-next 2/9] net: ipa: get rid of ipa->reg_addr Alex Elder
2023-02-08 20:56 ` [PATCH net-next 3/9] net: ipa: add some new IPA versions Alex Elder
2023-02-08 20:56 ` [PATCH net-next 4/9] net: ipa: tighten up IPA register validity checking Alex Elder
2023-02-08 20:56 ` [PATCH net-next 5/9] net: ipa: use bitmasks for GSI IRQ values Alex Elder
2023-02-08 20:56 ` [PATCH net-next 6/9] net: ipa: GSI register cleanup Alex Elder
2023-02-08 20:56 ` [PATCH net-next 7/9] net: ipa: start generalizing "ipa_reg" Alex Elder
2023-02-08 20:56 ` [PATCH net-next 8/9] net: ipa: generalize register offset functions Alex Elder
2023-02-08 20:56 ` [PATCH net-next 9/9] net: ipa: generalize register field functions Alex Elder
2023-02-10 8: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=167601901934.32230.173851279004955737.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andersson@kernel.org \
--cc=caleb.connolly@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).