From: <Andrei.Stefanescu@microchip.com>
To: rdunlap@infradead.org, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, broonie@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Dec 17 (regulator/mcp16502.c)
Date: Tue, 18 Dec 2018 09:28:28 +0000 [thread overview]
Message-ID: <366d42a1-ce66-c2ec-3007-40c72bd41a93@microchip.com> (raw)
In-Reply-To: <c7bd09d3-3c04-327e-6c0b-89ee058cced8@infradead.org>
Hi Randy,
Thank you for the email. The error should be fixed with this patch [1].
Best regards,
Andrei
[1] -
http://lists.infradead.org/pipermail/linux-arm-kernel/2018-December/621292.html
On 17.12.2018 18:03, Randy Dunlap wrote:
> On 12/17/18 3:09 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20181214:
>>
> on i386:
> # CONFIG_SUSPEND is not set
> CONFIG_PM=y
>
> CC drivers/regulator/mcp16502.o
> In file included from ../include/linux/device.h:23:0,
> from ../include/linux/gpio/driver.h:5,
> from ../include/asm-generic/gpio.h:13,
> from ../include/linux/gpio.h:62,
> from ../drivers/regulator/mcp16502.c:11:
> ../drivers/regulator/mcp16502.c:527:32: error: 'mcp16502_suspend_noirq' undeclared here (not in a function)
> SET_NOIRQ_SYSTEM_SLEEP_PM_OPS(mcp16502_suspend_noirq,
> ^
> ../include/linux/pm.h:342:19: note: in definition of macro 'SET_NOIRQ_SYSTEM_SLEEP_PM_OPS'
> .suspend_noirq = suspend_fn, \
> ^
> ../drivers/regulator/mcp16502.c:528:10: error: 'mcp16502_resume_noirq' undeclared here (not in a function)
> mcp16502_resume_noirq)
> ^
> ../include/linux/pm.h:343:18: note: in definition of macro 'SET_NOIRQ_SYSTEM_SLEEP_PM_OPS'
> .resume_noirq = resume_fn, \
> ^
>
>
>
prev parent reply other threads:[~2018-12-18 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 11:09 linux-next: Tree for Dec 17 Stephen Rothwell
2018-12-17 16:03 ` linux-next: Tree for Dec 17 (regulator/mcp16502.c) Randy Dunlap
2018-12-18 9:28 ` Andrei.Stefanescu [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=366d42a1-ce66-c2ec-3007-40c72bd41a93@microchip.com \
--to=andrei.stefanescu@microchip.com \
--cc=broonie@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).