From: Wolfram Sang <wsa@the-dreams.de>
To: Michal Marek <mmarek@suse.cz>
Cc: Richard Weinberger <richard@nod.at>,
Lee Jones <lee.jones@linaro.org>,
linux-next@vger.kernel.org, sameo@linux.intel.com,
Arnd Bergmann <arnd@arndb.de>,
yann.morin.1998@free.fr,
linux-kbuild <linux-kbuild@vger.kernel.org>,
"open list:I2C SUBSYSTEM" <linux-i2c@vger.kernel.org>,
user-mode-linux-devel
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: unmet direct dependencies in -next
Date: Mon, 10 Aug 2015 13:55:41 +0200 [thread overview]
Message-ID: <20150810115541.GA6479@katana> (raw)
In-Reply-To: <55C88738.80400@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
> 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.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-10 11:55 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 [this message]
2015-08-10 11:57 ` Michal Marek
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=20150810115541.GA6479@katana \
--to=wsa@the-dreams.de \
--cc=arnd@arndb.de \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=richard@nod.at \
--cc=sameo@linux.intel.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=yann.morin.1998@free.fr \
/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).