netdev - Re: [PATCH] [net-next] ipa: add remoteproc dependency

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: <a41bb573-f133-0188-275f-4637e10bbbaf@ieee.org>
Date:   Mon, 25 Jan 2021 09:33:04 -0600
From:   Alex Elder <elder@...e.org>
To:     Arnd Bergmann <arnd@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>
Cc:     Alex Elder <elder@...nel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        Arnd Bergmann <arnd@...db.de>,
        Networking <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] [net-next] ipa: add remoteproc dependency

On 1/25/21 9:30 AM, Arnd Bergmann wrote:
> On Mon, Jan 25, 2021 at 4:23 PM Bjorn Andersson
> <bjorn.andersson@...aro.org> wrote:
>>
>> On Mon 25 Jan 05:35 CST 2021, Arnd Bergmann wrote:
>>
>>> From: Arnd Bergmann <arnd@...db.de>
>>>
>>> Compile-testing without CONFIG_REMOTEPROC results in a build failure:
>>>
>>>>>> referenced by ipa_main.c
>>>>>>                net/ipa/ipa_main.o:(ipa_probe) in archive drivers/built-in.a
>>> ld.lld: error: undefined symbol: rproc_put
>>>>>> referenced by ipa_main.c
>>>>>>                net/ipa/ipa_main.o:(ipa_probe) in archive drivers/built-in.a
>>>>>> referenced by ipa_main.c
>>>>>>                net/ipa/ipa_main.o:(ipa_remove) in archive drivers/built-in.a
>>>
>>> Add a new dependency to avoid this.
>>>
>>
>> Afaict this should be addressed by:
>>
>> 86fdf1fc60e9 ("net: ipa: remove a remoteproc dependency")
>>
>> which is present in linux-next.
> 
> Ok, good. I was testing with next-20210122, which was
> still lacking that commit.

Yes, for various reasons this took a while to get incorporated.
It just got accepted over the weekend.  Thanks for mentioning it.

					-Alex

> 
>        Arnd
>