From: Michal Marek <mmarek-AlSwsSmVLrQ@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Cc: Richard Weinberger <richard-/L3Ra7n9ekc@public.gmane.org>,
Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
yann.morin.1998-GANU6spQydw@public.gmane.org,
linux-kbuild
<linux-kbuild-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"open list:I2C SUBSYSTEM"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
user-mode-linux-devel
<user-mode-linux-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: unmet direct dependencies in -next
Date: Mon, 10 Aug 2015 13:57:29 +0200 [thread overview]
Message-ID: <55C891A9.2080607@suse.cz> (raw)
In-Reply-To: <20150810115541.GA6479@katana>
On 2015-08-10 13:55, Wolfram Sang wrote:
>
>> The result of the given .config does not matter as much. The point of
>> the warnings is that there are missing select statements in the Kconfig
>> files.
>
> For the I2C part, I think they should rather depend on I2C_MUX.
> Selecting I2C should be rare, like when you really need that PMIC to
> boot.
Right, that's another way to fix it.
Michal
next prev parent reply other threads:[~2015-08-10 11:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 9:40 unmet direct dependencies in -next Richard Weinberger
[not found] ` <55C71FF5.1020902-/L3Ra7n9ekc@public.gmane.org>
2015-08-10 9:10 ` Lee Jones
2015-08-10 9:14 ` Richard Weinberger
[not found] ` <55C86B66.3020601-/L3Ra7n9ekc@public.gmane.org>
2015-08-10 11:12 ` Michal Marek
2015-08-10 11:24 ` Richard Weinberger
2015-08-10 11:55 ` Wolfram Sang
2015-08-10 11:57 ` Michal Marek [this message]
2016-01-02 22:01 ` Richard Weinberger
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=55C891A9.2080607@suse.cz \
--to=mmarek-alswssmvlrq@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kbuild-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=richard-/L3Ra7n9ekc@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=user-mode-linux-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org \
--cc=yann.morin.1998-GANU6spQydw@public.gmane.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).