From: Andy Gross <andy.gross@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Ohad Ben-Cohen <ohad@wizery.com>,
David Brown <david.brown@linaro.org>, Suman Anna <s-anna@ti.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: qmi: add CONFIG_NET dependency
Date: Thu, 8 Mar 2018 18:44:02 -0600 [thread overview]
Message-ID: <20180309004402.GA5910@hector.attlocal.net> (raw)
In-Reply-To: <20180222155833.1860318-1-arnd@arndb.de>
On Thu, Feb 22, 2018 at 04:57:38PM +0100, Arnd Bergmann wrote:
> Access to the socket API and the root network namespace is only available
> when networking is enabled:
>
> ERROR: "kernel_sendmsg" [drivers/soc/qcom/qmi_helpers.ko] undefined!
> ERROR: "sock_release" [drivers/soc/qcom/qmi_helpers.ko] undefined!
> ERROR: "sock_create_kern" [drivers/soc/qcom/qmi_helpers.ko] undefined!
> ERROR: "kernel_getsockname" [drivers/soc/qcom/qmi_helpers.ko] undefined!
> ERROR: "init_net" [drivers/soc/qcom/qmi_helpers.ko] undefined!
> ERROR: "kernel_recvmsg" [drivers/soc/qcom/qmi_helpers.ko] undefined!
>
> Adding a dependency on CONFIG_NET lets us build it in all randconfig
> builds.
>
> Fixes: 9b8a11e82615 ("soc: qcom: Introduce QMI encoder/decoder")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/remoteproc/Kconfig | 1 +
> drivers/soc/qcom/Kconfig | 2 +-
> samples/Kconfig | 1 +
> 3 files changed, 3 insertions(+), 1 deletion(-)
Acked-by: Andy Gross <andy.gross@linaro.org>
prev parent reply other threads:[~2018-03-09 0:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 15:57 Arnd Bergmann
2018-03-09 0:44 ` Andy Gross [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=20180309004402.GA5910@hector.attlocal.net \
--to=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=s-anna@ti.com \
--cc=srinivas.kandagatla@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®