linux-kernel - Re: [PATCH net-next 0/2] net: ipa: allow different firmware names

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <161861340973.29090.15022740870858243639.git-patchwork-notify@kernel.org>
Date:   Fri, 16 Apr 2021 22:50:09 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Alex Elder <elder@...aro.org>
Cc:     davem@...emloft.net, kuba@...nel.org, robh+dt@...nel.org,
        bjorn.andersson@...aro.org, agross@...nel.org, elder@...nel.org,
        linux-arm-msm@...r.kernel.org, netdev@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 0/2] net: ipa: allow different firmware names

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