From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mmc@vger.kernel.org, Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: linux-next: Tree for Dec 21 (mmc/host/sdhci-omap.c)
Date: Fri, 21 Dec 2018 09:35:56 -0800 [thread overview]
Message-ID: <16ca363b-92a7-d1cd-8460-21514e0e964b@infradead.org> (raw)
In-Reply-To: <20181221193244.3a6ed685@canb.auug.org.au>
On 12/21/18 12:32 AM, Stephen Rothwell wrote:
> Hi all,
>
> News: there will be no linux-next release until Jan 2. Have a good break.
>
> Changes since 20181220:
>
on x86_64:
This change to drivers/mmc/host/Kconfig:
config MMC_SDHCI_OMAP
tristate "TI SDHCI Controller Support"
depends on MMC_SDHCI_PLTFM && OF
+ select THERMAL
+ select TI_SOC_THERMAL
causes a Kconfig warning:
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 [=y] && MMC_SDHCI_PLTFM [=y] && OF [=y]
because ARCH_HAS_BANDGAP is not set (nor is COMPILE_TEST).
--
~Randy
next prev parent reply other threads:[~2018-12-21 17:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 8:32 linux-next: Tree for Dec 21 Stephen Rothwell
2018-12-21 16:21 ` Guenter Roeck
2018-12-21 16:33 ` Ard Biesheuvel
2018-12-21 20:57 ` Florian Westphal
2018-12-22 6:43 ` Chandan Rajendra
2018-12-24 8:20 ` Greg Kroah-Hartman
2018-12-31 14:01 ` Vinod Koul
2018-12-21 16:37 ` linux-next: Tree for Dec 21 (acpi without CONFIG_PCI) Randy Dunlap
[not found] ` <CAK9iUCO_Pk3eYH+hyMuqU6weDsbzC9Sg1Z719fm8u_3Oh7s-iQ@mail.gmail.com>
2018-12-21 17:26 ` Randy Dunlap
2018-12-21 17:43 ` Randy Dunlap
2018-12-22 0:05 ` Sinan Kaya
2018-12-21 18:28 ` Randy Dunlap
2018-12-22 0:04 ` Sinan Kaya
2018-12-21 17:08 ` linux-next: Tree for Dec 21 (nvdimm/security.o) Randy Dunlap
2018-12-21 18:51 ` Dan Williams
2018-12-21 21:01 ` Dan Williams
2018-12-21 17:35 ` Randy Dunlap [this message]
2018-12-21 18:02 ` linux-next: Tree for Dec 21 (SND_HDA_INTEL_DSP_DETECTION) Randy Dunlap
2018-12-21 20:39 ` [alsa-devel] " Pierre-Louis Bossart
2018-12-21 18:36 ` linux-next: Tree for Dec 21 (FB_BACKLIGHT) 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=16ca363b-92a7-d1cd-8460-21514e0e964b@infradead.org \
--to=rdunlap@infradead.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-next@vger.kernel.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).