From: Wolfram Sang <wsa@the-dreams.de>
To: Jim Davis <jim.epost@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
david.e.box@linux.intel.com, linux-i2c@vger.kernel.org
Subject: Re: randconfig build error with next-20150127, in drivers/i2c/busses/i2c-designware-baytrail.c
Date: Wed, 28 Jan 2015 07:59:29 +0100 [thread overview]
Message-ID: <20150128065929.GA1086@katana> (raw)
In-Reply-To: <CA+r1ZhisCd7+LJ0gm-NLPJ+UE-FEuEWFQqDqcy7KPp2tD_bveA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 206 bytes --]
On Tue, Jan 27, 2015 at 04:41:44PM -0700, Jim Davis wrote:
> Building with the attached random configuration file,
A proper Kconfig dependency fix has already been added and is in
linux-next as of today.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-01-28 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 23:41 randconfig build error with next-20150127, in drivers/i2c/busses/i2c-designware-baytrail.c Jim Davis
2015-01-28 6:59 ` Wolfram Sang [this message]
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=20150128065929.GA1086@katana \
--to=wsa@the-dreams.de \
--cc=david.e.box@linux.intel.com \
--cc=jim.epost@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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).