From: Kalle Valo <kvalo@codeaurora.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Brown <david.brown@linaro.org>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ath10k@lists.infradead.org, Andy Gross <andy.gross@linaro.org>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Niklas Cassel <niklas.cassel@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
davem@davemloft.net
Subject: Re: [GIT] Networking
Date: Wed, 24 Oct 2018 10:30:09 +0300 [thread overview]
Message-ID: <87pnvzu7i6.fsf@codeaurora.org> (raw)
In-Reply-To: <CAHk-=whuhCGujWKO8JObGQaSdWOpJBXdkM-B-vD80QZifveScw@mail.gmail.com> (Linus Torvalds's message of "Wed, 24 Oct 2018 07:01:31 +0100")
+ linux-wireless, ath10k, niklas, jeff, andy, david
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Wed, Oct 24, 2018 at 4:30 AM David Miller <davem@davemloft.net> wrote:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
>
> Hmm. Tentatively pulled, but there's something wrong with the Kconfig rules.
>
> Doing "make allmodconfig" (not even the build itself, just the config
> phase), I get
>
> 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])
>
> because I'm obviously not building on ARCH_QCOM.
>
> I suspect that QCOM_QMI_HELPERS needs to have
>
> depends on (ARCH_QCOM || COMPILE_TEST) && NET
>
> or similar. I'll see if this builds for me at all despite the Kconfig warning.
I had missed this warning, sorry about that. Jeff reported the same
problem while I was on vacation and according to Niklas[1] it should be
fixed by this commit in linux-next:
ccfb464cd106 ("soc: qcom: Allow COMPILE_TEST of qcom SoC Kconfigs")
I'm hoping you will get the commit during this merge window but not sure
about that and via which tree it would come. Adding Andy and David who
hopefully know more.
[1] http://lists.infradead.org/pipermail/ath10k/2018-October/012330.html
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next parent reply other threads:[~2018-10-24 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181023.202921.1185045750138652543.davem@davemloft.net>
[not found] ` <CAHk-=whuhCGujWKO8JObGQaSdWOpJBXdkM-B-vD80QZifveScw@mail.gmail.com>
2018-10-24 7:30 ` Kalle Valo [this message]
[not found] ` <CAHk-=wh2H9jE2RXibQgWs3_Q539roj62_gzPXKjnhhKqSFcw2g@mail.gmail.com>
2018-10-24 7:50 ` [GIT] Networking Kalle Valo
2018-10-24 8:05 ` Kalle Valo
2018-10-24 13:28 ` Andy Gross
[not found] ` <CAPBZ5Qen9ak4eFqdHEKNVoGBWUtohu_hwYxZ2cwmyAU=a8Mv9A@mail.gmail.com>
2018-10-24 13:40 ` Linus Torvalds
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=87pnvzu7i6.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=andy.gross@linaro.org \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=david.brown@linaro.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.cassel@linaro.org \
--cc=torvalds@linux-foundation.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