From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Baruch Siach <baruch@tkos.co.il>,
linux-i2c@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: linux-next: Tree for Oct 21 (drivers/i2c/busses/i2c-designware-platdrv.c)
Date: Thu, 22 Oct 2015 08:47:32 +0300 [thread overview]
Message-ID: <56287874.40102@linux.intel.com> (raw)
In-Reply-To: <5627F55E.1010009@infradead.org>
Hi
On 10/21/2015 11:28 PM, Randy Dunlap wrote:
> On 10/20/15 23:16, Stephen Rothwell wrote:
>> Hi all,
>>
>> There will be no linux-next releases after tomorrow until Nov 2 (kernel
>> summit).
>>
>> Changes since 20151020:
>>
>
> on i386 or x86_64:
>
> when CONFIG_PM_SLEEP is not enabled:
>
> ../drivers/i2c/busses/i2c-designware-platdrv.c:340:13: error: 'dw_i2c_plat_prepare' undeclared here (not in a function)
> .prepare = dw_i2c_plat_prepare,
> ^
> ../drivers/i2c/busses/i2c-designware-platdrv.c:341:14: error: 'dw_i2c_plat_complete' undeclared here (not in a function)
> .complete = dw_i2c_plat_complete,
> ^
Here's the fix for this:
http://marc.info/?l=linux-i2c&m=144541136917692&w=2
--
Jarkko
next prev parent reply other threads:[~2015-10-22 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 6:16 linux-next: Tree for Oct 21 Stephen Rothwell
2015-10-21 20:28 ` linux-next: Tree for Oct 21 (drivers/i2c/busses/i2c-designware-platdrv.c) Randy Dunlap
2015-10-22 5:47 ` Jarkko Nikula [this message]
2015-10-21 20:54 ` linux-next: Tree for Oct 21 (regmap-spmi.c caused by QCOM_SPMI_TEMP_ALARM) Randy Dunlap
2015-10-21 22:12 ` Stephen Boyd
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=56287874.40102@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baruch@tkos.co.il \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--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.