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/4] net: ipa: don't use fixed table sizes
Date: Thu, 27 Oct 2022 12:00:17 +0000 [thread overview]
Message-ID: <166687201757.29716.7404783392276656944.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221025195143.255934-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 25 Oct 2022 14:51:39 -0500 you wrote:
> Currently, routing and filter tables are assumed to have a fixed
> size for all platforms. In fact, these tables can support many more
> entries than what has been assumed; the only limitation is the size
> of the IPA-resident memory regions that contain them.
>
> This series rearranges things so that the size of the table is
> determined from the memory region size defined in configuration
> data, rather than assuming it is fixed.
>
> [...]
Here is the summary with links:
- [net-next,1/4] net: ipa: record the route table size in the IPA structure
https://git.kernel.org/netdev/net-next/c/fc094058ce01
- [net-next,2/4] net: ipa: determine route table size from memory region
https://git.kernel.org/netdev/net-next/c/0439e6743c5c
- [net-next,3/4] net: ipa: don't assume 8 modem routing table entries
https://git.kernel.org/netdev/net-next/c/8defab8bdfb1
- [net-next,4/4] net: ipa: determine filter table size from memory region
https://git.kernel.org/netdev/net-next/c/f787d8483015
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-10-27 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 19:51 [PATCH net-next 0/4] net: ipa: don't use fixed table sizes Alex Elder
2022-10-25 19:51 ` [PATCH net-next 1/4] net: ipa: record the route table size in the IPA structure Alex Elder
2022-10-25 19:51 ` [PATCH net-next 2/4] net: ipa: determine route table size from memory region Alex Elder
2022-10-25 19:51 ` [PATCH net-next 3/4] net: ipa: don't assume 8 modem routing table entries Alex Elder
2022-10-25 19:51 ` [PATCH net-next 4/4] net: ipa: determine filter table size from memory region Alex Elder
2022-10-27 12:00 ` 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=166687201757.29716.7404783392276656944.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