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, elder@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] net: ipa: update configuration data
Date: Fri, 19 Mar 2021 20:40:08 +0000 [thread overview]
Message-ID: <161618640891.3803.15579900708987919124.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210319152422.1803714-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 19 Mar 2021 10:24:17 -0500 you wrote:
> Each IPA version has a "data" file defining how various things are
> configured. This series gathers a few updates to this information:
> - The first patch makes all configuration data constant
> - The second fixes an incorrect (but seemingly harmless) value
> - The third simplifies things a bit by using implicit zero
> initialization for memory regions that are empty
> - The fourth adds definitions for memory regions that exist but
> are not yet used
> - The fifth use configuration data rather than conditional code to
> set some bus parameters
>
> [...]
Here is the summary with links:
- [net-next,1/5] net: ipa: make all configuration data constant
https://git.kernel.org/netdev/net-next/c/e4a9f45b0be5
- [net-next,2/5] net: ipa: fix canary count for SC7180 UC_INFO region
https://git.kernel.org/netdev/net-next/c/22e3b314302c
- [net-next,3/5] net: ipa: don't define empty memory regions
https://git.kernel.org/netdev/net-next/c/8f692169b138
- [net-next,4/5] net: ipa: define some new memory regions
https://git.kernel.org/netdev/net-next/c/2ef88644e5d4
- [net-next,5/5] net: ipa: define QSB limits in configuration data
https://git.kernel.org/netdev/net-next/c/37537fa8e973
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-03-19 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 15:24 Alex Elder
2021-03-19 15:24 ` [PATCH net-next 1/5] net: ipa: make all configuration data constant Alex Elder
2021-03-19 15:24 ` [PATCH net-next 2/5] net: ipa: fix canary count for SC7180 UC_INFO region Alex Elder
2021-03-19 15:24 ` [PATCH net-next 3/5] net: ipa: don't define empty memory regions Alex Elder
2021-03-19 15:24 ` [PATCH net-next 4/5] net: ipa: define some new " Alex Elder
2021-03-19 15:24 ` [PATCH net-next 5/5] net: ipa: define QSB limits in configuration data Alex Elder
2021-03-19 20:40 ` 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=161618640891.3803.15579900708987919124.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 \
/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
Powered by JetHome