From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, kuba@kernel.org, robh+dt@kernel.org,
bjorn.andersson@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 0/2] net: ipa: allow different firmware names
Date: Fri, 16 Apr 2021 22:50:09 +0000 [thread overview]
Message-ID: <161861340973.29090.15022740870858243639.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210416130850.1970247-1-elder@linaro.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 16 Apr 2021 08:08:48 -0500 you wrote:
> Add the ability to define a "firmware-name" property in the IPA DT
> node, specifying an alternate name to use for the firmware file.
> Used only if the AP (Trust Zone) does early IPA initialization.
>
> -Alex
>
> Alex Elder (2):
> dt-bindings: net: qcom,ipa: add firmware-name property
> net: ipa: optionally define firmware name via DT
>
> [...]
Here is the summary with links:
- [net-next,1/2] dt-bindings: net: qcom,ipa: add firmware-name property
https://git.kernel.org/netdev/net-next/c/d8604b209e9b
- [net-next,2/2] net: ipa: optionally define firmware name via DT
https://git.kernel.org/netdev/net-next/c/9ce062ba6a8d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-04-16 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 13:08 [PATCH net-next 0/2] net: ipa: allow different firmware names Alex Elder
2021-04-16 13:08 ` [PATCH net-next 1/2] dt-bindings: net: qcom,ipa: add firmware-name property Alex Elder
2021-04-16 13:08 ` [PATCH net-next 2/2] net: ipa: optionally define firmware name via DT Alex Elder
2021-04-16 22:50 ` patchwork-bot+netdevbpf [this message]
2021-05-26 19:03 ` [PATCH net-next 0/2] net: ipa: allow different firmware names patchwork-bot+linux-arm-msm
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=161861340973.29090.15022740870858243639.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=elder@kernel.org \
--cc=elder@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=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.