From: Kalle Valo <kvalo@codeaurora.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ath11k@lists.infradead.org
Subject: Re: linux-next: Tree for Sep 9 (ath11k)
Date: Thu, 10 Sep 2020 07:23:48 +0000 [thread overview]
Message-ID: <0101017476e62656-22a95a04-af3b-4d23-b454-70e8a6d8a45c-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <0101017476bd06e1-16ca4de8-647e-4423-9630-753fb5675e8b-000000@us-west-2.amazonses.com> (Kalle Valo's message of "Thu, 10 Sep 2020 06:38:53 +0000")
Kalle Valo <kvalo@codeaurora.org> writes:
> Randy Dunlap <rdunlap@infradead.org> writes:
>
>> On 9/9/20 3:26 AM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20200908:
>>>
>>
>> on x86_64:
>>
>> ld: drivers/net/wireless/ath/ath11k/core.o: in function `ath11k_core_init':
>> core.c:(.text+0x121f): undefined reference to `rproc_get_by_phandle'
>
> This is because CONFIG_REMOTEPROC is not, I'll fix the dependency in
> ath11k. Thanks for the report.
Patch sent:
ath11k: fix link error when CONFIG_REMOTEPROC is disabled
https://patchwork.kernel.org/patch/11766849/
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-09-10 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 10:26 linux-next: Tree for Sep 9 Stephen Rothwell
2020-09-09 16:04 ` linux-next: Tree for Sep 9 (drivers/usb/typec/mux/intel_pmc_mux.c) Randy Dunlap
2020-09-10 10:49 ` Heikki Krogerus
2020-09-09 17:48 ` linux-next: Tree for Sep 9 (ath11k) Randy Dunlap
2020-09-10 6:38 ` Kalle Valo
[not found] ` <0101017476bd06e1-16ca4de8-647e-4423-9630-753fb5675e8b-000000@us-west-2.amazonses.com>
2020-09-10 7:23 ` Kalle Valo [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=0101017476e62656-22a95a04-af3b-4d23-b454-70e8a6d8a45c-000000@us-west-2.amazonses.com \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).