From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, kuba@kernel.org, bjorn.andersson@linaro.org,
evgreen@chromium.org, cpratapa@codeaurora.org,
subashab@codeaurora.org, elder@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 00/11] net: ipa: memory region rework, part 1
Date: Wed, 09 Jun 2021 23:10:04 +0000 [thread overview]
Message-ID: <162328020463.6274.14788072203026589858.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210609223503.2649114-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 9 Jun 2021 17:34:52 -0500 you wrote:
> This is the first portion of a very long series of patches that has
> been split in two. Once these patches are accepted, I'll post the
> remaining patches.
>
> The combined series reworks the way memory regions are defined in
> the configuration data, and in the process solidifies code that
> ensures configurations are valid.
>
> [...]
Here is the summary with links:
- [net-next,01/11] net: ipa: define IPA_MEM_END_MARKER
https://git.kernel.org/netdev/net-next/c/f636a83662ff
- [net-next,02/11] net: ipa: store memory region id in descriptor
https://git.kernel.org/netdev/net-next/c/14ab6a208c11
- [net-next,03/11] net: ipa: validate memory regions unconditionally
https://git.kernel.org/netdev/net-next/c/0300df2d9d24
- [net-next,04/11] net: ipa: separate memory validation from initialization
https://git.kernel.org/netdev/net-next/c/98334d2a3ba4
- [net-next,05/11] net: ipa: separate region range check from other validation
https://git.kernel.org/netdev/net-next/c/5e57c6c5a349
- [net-next,06/11] net: ipa: validate memory regions at init time
https://git.kernel.org/netdev/net-next/c/2f9be1e90860
- [net-next,07/11] net: ipa: pass memory configuration data to ipa_mem_valid()
https://git.kernel.org/netdev/net-next/c/1eec767746e5
- [net-next,08/11] net: ipa: introduce ipa_mem_id_optional()
https://git.kernel.org/netdev/net-next/c/d39ffb97079b
- [net-next,09/11] net: ipa: validate memory regions based on version
https://git.kernel.org/netdev/net-next/c/75bcfde6c113
- [net-next,10/11] net: ipa: flag duplicate memory regions
https://git.kernel.org/netdev/net-next/c/eadf7f937614
- [net-next,11/11] net: ipa: use bitmap to check for missing regions
https://git.kernel.org/netdev/net-next/c/6857b02392ab
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:[~2021-06-09 23:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 22:34 Alex Elder
2021-06-09 22:34 ` [PATCH net-next 01/11] net: ipa: define IPA_MEM_END_MARKER Alex Elder
2021-06-09 22:34 ` [PATCH net-next 02/11] net: ipa: store memory region id in descriptor Alex Elder
2021-06-09 22:34 ` [PATCH net-next 03/11] net: ipa: validate memory regions unconditionally Alex Elder
2021-06-09 22:34 ` [PATCH net-next 04/11] net: ipa: separate memory validation from initialization Alex Elder
2021-06-09 22:34 ` [PATCH net-next 05/11] net: ipa: separate region range check from other validation Alex Elder
2021-06-09 22:34 ` [PATCH net-next 06/11] net: ipa: validate memory regions at init time Alex Elder
2021-06-09 22:34 ` [PATCH net-next 07/11] net: ipa: pass memory configuration data to ipa_mem_valid() Alex Elder
2021-06-09 22:35 ` [PATCH net-next 08/11] net: ipa: introduce ipa_mem_id_optional() Alex Elder
2021-06-09 22:35 ` [PATCH net-next 09/11] net: ipa: validate memory regions based on version Alex Elder
2021-06-09 22:35 ` [PATCH net-next 10/11] net: ipa: flag duplicate memory regions Alex Elder
2021-06-09 22:35 ` [PATCH net-next 11/11] net: ipa: use bitmap to check for missing regions Alex Elder
2021-06-09 23: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=162328020463.6274.14788072203026589858.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=subashab@codeaurora.org \
/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
all inboxes | Powered by JetHome®