From: Randy Dunlap <rdunlap@infradead.org>
To: LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
linux-omap@vger.kernel.org
Cc: Eduardo Valentin <edubezval@gmail.com>, Keerthy <j-keerthy@ti.com>
Subject: linux-5.0-rc3, ti-soc-thermal: unmet dependencies Kconfig warning
Date: Fri, 25 Jan 2019 22:54:11 -0800 [thread overview]
Message-ID: <8baafd04-eda0-778d-84d2-7ccc1d07db6b@infradead.org> (raw)
Hi,
FYI, I'm seeing this Kconfig warning in 5.0-rc3:
WARNING: unmet direct dependencies detected for TI_SOC_THERMAL
Depends on [n]: THERMAL [=y] && (ARCH_HAS_BANDGAP || COMPILE_TEST [=n]) && HAS_IOMEM [=y]
Selected by [m]:
- MMC_SDHCI_OMAP [=m] && MMC [=m] && MMC_SDHCI_PLTFM [=m] && OF [=y]
Maybe there is already a patch for this?
thanks,
--
~Randy
next reply other threads:[~2019-01-26 6:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 6:54 Randy Dunlap [this message]
2019-01-28 16:34 ` linux-5.0-rc3, ti-soc-thermal: unmet dependencies Kconfig warning Tony Lindgren
2019-01-29 3:39 ` Keerthy
2019-01-29 14:48 ` Tony Lindgren
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=8baafd04-eda0-778d-84d2-7ccc1d07db6b@infradead.org \
--to=rdunlap@infradead.org \
--cc=edubezval@gmail.com \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).