From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andersson@kernel.org,
konrad.dybcio@linaro.org, agross@kernel.org, elder@kernel.org,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/5] net: ipa: change GSI firmware load specification
Date: Fri, 18 Nov 2022 06:30:24 +0000 [thread overview]
Message-ID: <166875302462.3603.16365158346185465889.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221116073257.34010-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 16 Nov 2022 01:32:51 -0600 you wrote:
> Version 3 just adds reviewed-by tags for Krzysztof Kozlowski.
>
> Version 2 of this series modifies the first patch only. One section
> in the description is reworded, and the example now consistenly
> describes the SC7180 SoC, both as suggested by Krzysztof.
>
> Currently, GSI firmware must be loaded for IPA before it can be
> used--either by the modem, or by the AP. New hardware supports a
> third option, with the bootloader taking responsibility for loading
> GSI firmware. In that case, neither the AP nor the modem needs to
> do that.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/5] dt-bindings: net: qcom,ipa: deprecate modem-init
https://git.kernel.org/netdev/net-next/c/4ca0c6474f71
- [net-next,v3,2/5] net: ipa: encapsulate decision about firmware load
https://git.kernel.org/netdev/net-next/c/50f803d4aa71
- [net-next,v3,3/5] net: ipa: introduce "qcom,gsi-loader" property
https://git.kernel.org/netdev/net-next/c/07f2f8e1b747
- [net-next,v3,4/5] dt-bindings: net: qcom,ipa: support skipping GSI firmware load
https://git.kernel.org/netdev/net-next/c/a49c3ab7d75f
- [net-next,v3,5/5] net: ipa: permit GSI firmware loading to be skipped
https://git.kernel.org/netdev/net-next/c/7569805ec26e
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-11-18 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 7:32 [PATCH net-next v3 0/5] net: ipa: change GSI firmware load specification Alex Elder
2022-11-16 7:32 ` [PATCH net-next v3 1/5] dt-bindings: net: qcom,ipa: deprecate modem-init Alex Elder
2022-11-16 7:32 ` [PATCH net-next v3 2/5] net: ipa: encapsulate decision about firmware load Alex Elder
2022-11-16 7:32 ` [PATCH net-next v3 3/5] net: ipa: introduce "qcom,gsi-loader" property Alex Elder
2022-11-16 7:32 ` [PATCH net-next v3 4/5] dt-bindings: net: qcom,ipa: support skipping GSI firmware load Alex Elder
2022-11-16 7:32 ` [PATCH net-next v3 5/5] net: ipa: permit GSI firmware loading to be skipped Alex Elder
2022-11-18 6:30 ` 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=166875302462.3603.16365158346185465889.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.