From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nandor Han <nandor.han@vaisala.com>,
Andy Yan <andy.yan@rock-chips.com>,
Sebastian Reichel <sre@kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 28 (power/reset/reboot-mode)
Date: Fri, 28 Jun 2019 16:46:47 -0700 [thread overview]
Message-ID: <bb7b5d1a-97b5-7f74-4075-eeb290fd9508@infradead.org> (raw)
In-Reply-To: <20190628203840.1f74e739@canb.auug.org.au>
On 6/28/19 3:38 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190627:
>
on x86_64:
when CONFIG_OF is not set/enabled, but
CONFIG_NVMEM_REBOOT_MODE=m selects REBOOT_MODE:
CC [M] drivers/power/reset/reboot-mode.o
../drivers/power/reset/reboot-mode.c: In function ‘reboot_mode_register’:
../drivers/power/reset/reboot-mode.c:72:2: error: implicit declaration of function ‘for_each_property_of_node’ [-Werror=implicit-function-declaration]
for_each_property_of_node(np, prop) {
^
../drivers/power/reset/reboot-mode.c:72:38: error: expected ‘;’ before ‘{’ token
for_each_property_of_node(np, prop) {
^
../drivers/power/reset/reboot-mode.c:109:1: warning: label ‘error’ defined but not used [-Wunused-label]
error:
^
../drivers/power/reset/reboot-mode.c:67:9: warning: unused variable ‘len’ [-Wunused-variable]
size_t len = strlen(PREFIX);
^
../drivers/power/reset/reboot-mode.c: At top level:
../drivers/power/reset/reboot-mode.c:42:12: warning: ‘reboot_mode_notify’ defined but not used [-Wunused-function]
static int reboot_mode_notify(struct notifier_block *this,
^
--
~Randy
prev parent reply other threads:[~2019-06-28 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 10:38 linux-next: Tree for Jun 28 Stephen Rothwell
2019-06-28 20:52 ` linux-next: Tree for Jun 28 (kernel/bpf/cgroup.c) Randy Dunlap
2019-07-05 22:23 ` Randy Dunlap
2019-06-28 23:46 ` Randy Dunlap [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=bb7b5d1a-97b5-7f74-4075-eeb290fd9508@infradead.org \
--to=rdunlap@infradead.org \
--cc=andy.yan@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nandor.han@vaisala.com \
--cc=sfr@canb.auug.org.au \
--cc=sre@kernel.org \
/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
all inboxes | Powered by JetHome®