From: Wolfram Sang <wsa@the-dreams.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
M'boumba Cedric Madianga <cedric.madianga@gmail.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 31 (drivers/i2c/busses/i2c-stm32f7.c)
Date: Fri, 31 Jan 2020 08:52:05 +0100 [thread overview]
Message-ID: <20200131075205.GF1028@ninjato> (raw)
In-Reply-To: <7cd84961-d1f5-03eb-2e00-8f51b2f7121d@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
> on i386:
>
> when CONFIG_I2C is not set/enabled:
>
> ../drivers/i2c/busses/i2c-stm32f7.c: In function ‘stm32f7_i2c_suspend’:
> ../drivers/i2c/busses/i2c-stm32f7.c:2199:44: error: ‘struct dev_pm_info’ has no member named ‘wakeup_path’
> if (!device_may_wakeup(dev) && !dev->power.wakeup_path) {
> ^
> ../drivers/i2c/busses/i2c-stm32f7.c: In function ‘stm32f7_i2c_resume’:
> ../drivers/i2c/busses/i2c-stm32f7.c:2218:44: error: ‘struct dev_pm_info’ has no member named ‘wakeup_path’
> if (!device_may_wakeup(dev) && !dev->power.wakeup_path) {
I dropped/reverted this patch already. Sorry for the inconvenience!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-31 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 4:06 linux-next: Tree for Jan 31 Stephen Rothwell
2020-01-31 7:27 ` linux-next: Tree for Jan 31 (drivers/watchdog/da9062_wdt.c) Randy Dunlap
2020-01-31 7:49 ` linux-next: Tree for Jan 31 (drivers/i2c/busses/i2c-stm32f7.c) Randy Dunlap
2020-01-31 7:52 ` 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=20200131075205.GF1028@ninjato \
--to=wsa@the-dreams.de \
--cc=cedric.madianga@gmail.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 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).