All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"David E. Box" <david.e.box@linux.intel.com>,
	linux-i2c@vger.kernel.org
Subject: Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c)
Date: Tue, 17 Feb 2015 20:11:58 +0100	[thread overview]
Message-ID: <20150217191153.GA1616@katana> (raw)
In-Reply-To: <54E38840.5060306@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 376 bytes --]

Randy,

thanks for the report!

> I suppose someone could make that:
> 
> 	depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI
> 
> or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol.

I'll wait a day for input from David what he prefers, because I don't
own/know this platform. If there is no response, I'll apply the first
solution.

   Wolfram


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-02-17 19:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17  5:02 linux-next: Tree for Feb 17 Stephen Rothwell
2015-02-17 17:20 ` linux-next: Tree for Feb 17 (mips build failures) Guenter Roeck
2015-02-17 20:37   ` Stephen Rothwell
2015-02-18  9:14     ` Markos Chandras
2015-02-18  9:14       ` Markos Chandras
2015-02-18 13:54       ` Guenter Roeck
2015-02-18 14:02         ` Markos Chandras
2015-02-18 14:02           ` Markos Chandras
2015-02-17 18:28 ` linux-next: Tree for Feb 17 (i2c-designware-baytrail.c) Randy Dunlap
2015-02-17 19:11   ` Wolfram Sang [this message]
2015-02-17 20:59     ` David E. Box

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=20150217191153.GA1616@katana \
    --to=wsa@the-dreams.de \
    --cc=david.e.box@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.