ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <niklas.cassel@linaro.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: ath10k@lists.infradead.org, Kalle Valo <kvalo@codeaurora.org>
Subject: Re: ath10k: Kconfig build warnings
Date: Tue, 16 Oct 2018 22:03:11 +0200	[thread overview]
Message-ID: <20181016200311.GA15036@centauri.lan> (raw)
In-Reply-To: <d0a66e5c6c5cb385c07588859bac6a1d715bb435.camel@intel.com>

On Mon, Oct 15, 2018 at 03:07:18PM -0700, Jeff Kirsher wrote:
> Not sure if you aware, with David Miller's latest net-next tree, doing a
> 'make allmodconfig' produces the following Kconfig errors:
> 
> [15:06:06]$ make allmodconfig
> scripts/kconfig/conf  --allmodconfig Kconfig
> 
> WARNING: unmet direct dependencies detected for QCOM_QMI_HELPERS
>   Depends on [n]: ARCH_QCOM && NET [=y]
>   Selected by [m]:
>   - ATH10K_SNOC [=m] && NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_ATH
> [=y] && ATH10K [=m] && (ARCH_QCOM || COMPILE_TEST [=y])
> #
> # configuration written to .config
> #

Hello Jeff,

I believe this will be fixed by:
ccfb464cd106 ("soc: qcom: Allow COMPILE_TEST of qcom SoC Kconfigs")

Which is currently in linux-next.


Kind regards,
Niklas

> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

      reply	other threads:[~2018-10-16 20:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 22:07 ath10k: Kconfig build warnings Jeff Kirsher
2018-10-16 20:03 ` Niklas Cassel [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=20181016200311.GA15036@centauri.lan \
    --to=niklas.cassel@linaro.org \
    --cc=ath10k@lists.infradead.org \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=kvalo@codeaurora.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