linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.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 Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andy Gross <agross@kernel.org>,
	linux-arm-msm@vger.kernel.org
Subject: Re: linux-next: Tree for Mar 16 (drivers/soc/qcom/)
Date: Mon, 16 Mar 2020 15:10:32 -0700	[thread overview]
Message-ID: <20200316221032.GF1214176@minitux> (raw)
In-Reply-To: <4bf2d095-e416-7e39-b514-3a1a9b4248dd@infradead.org>

On Mon 16 Mar 10:34 PDT 2020, Randy Dunlap wrote:

> On 3/16/20 12:30 AM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20200313:
> > 
> 
> on i386 or x86_64:
> 
> WARNING: unmet direct dependencies detected for QCOM_QMI_HELPERS
>   Depends on [n]: NET [=n]
>   Selected by [y]:
>   - QCOM_PDR_HELPERS [=y]
> 
> causing:
> 
> ld: drivers/soc/qcom/qmi_interface.o: in function `qmi_send_new_lookup':
> qmi_interface.c:(.text+0xd3): undefined reference to `kernel_sendmsg'
> ld: drivers/soc/qcom/qmi_interface.o: in function `qmi_send_new_server':
> qmi_interface.c:(.text+0x1b6): undefined reference to `kernel_sendmsg'
> ld: drivers/soc/qcom/qmi_interface.o: in function `qmi_sock_create':
> qmi_interface.c:(.text+0x2f2): undefined reference to `init_net'
> ld: qmi_interface.c:(.text+0x2f9): undefined reference to `sock_create_kern'
> ld: qmi_interface.c:(.text+0x319): undefined reference to `kernel_getsockname'
> ld: qmi_interface.c:(.text+0x33e): undefined reference to `sock_release'
> ld: drivers/soc/qcom/qmi_interface.o: in function `qmi_send_message.isra.4':
> qmi_interface.c:(.text+0x45f): undefined reference to `kernel_sendmsg'
> ld: drivers/soc/qcom/qmi_interface.o: in function `qmi_data_ready_work':
> qmi_interface.c:(.text+0x7dc): undefined reference to `kernel_recvmsg'
> ld: qmi_interface.c:(.text+0x877): undefined reference to `sock_release'
> ld: drivers/soc/qcom/qmi_interface.o: in function `qmi_handle_release':
> qmi_interface.c:(.text+0x1018): undefined reference to `sock_release'
> 
> 
> 
> 
> All caused by QCOM_APR, which selects QCOM_PDR_HELPERS,
> and that one selects QCOM_QMI_HELPERS, which depends on NET, but:
> # CONFIG_NET is not set
> 
> Full randconfig file is attached.
> 
> -- 
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@infradead.org>

Thanks Randy, I've added the necessary dependency for QCOM_APR.

Regards,
Bjorn


  reply	other threads:[~2020-03-16 22:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16  7:30 linux-next: Tree for Mar 16 Stephen Rothwell
2020-03-16 17:34 ` linux-next: Tree for Mar 16 (drivers/soc/qcom/) Randy Dunlap
2020-03-16 22:10   ` Bjorn Andersson [this message]
2020-03-16 17:48 ` linux-next: Tree for Mar 16 (arch/x86/mm/ioremap.o) Randy Dunlap
2020-03-18 15:17   ` Borislav Petkov
2020-03-18 18:34     ` [PATCH] x86/ioremap: Fix CONFIG_EFI=n build Borislav Petkov
2020-03-18 19:30       ` Randy Dunlap
2020-03-18 19:34         ` Borislav Petkov
2020-03-18 19:35           ` Randy Dunlap

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=20200316221032.GF1214176@minitux \
    --to=bjorn.andersson@linaro.org \
    --cc=agross@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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).