From: Fengguang Wu <fengguang.wu@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: next-20140312 - build error in drivers/acpi/sleep.c
Date: Fri, 14 Mar 2014 08:08:13 +0800 [thread overview]
Message-ID: <20140314000813.GA8649@localhost> (raw)
In-Reply-To: <1431943.FB4azhDoEG@vostro.rjw.lan>
On Thu, Mar 13, 2014 at 10:23:51PM +0100, Rafael J. Wysocki wrote:
> On Thursday, March 13, 2014 02:48:31 PM Valdis Kletnieks wrote:
> > Seen in the most recent linux-next with a CONFIG_SUSPEND=n .config:
> >
> > CC drivers/acpi/sleep.o
> > drivers/acpi/sleep.c: In function 'acpi_sleep_init':
> > drivers/acpi/sleep.c:808:2: error: implicit declaration of function 'acpi_sleep_state_supported' [-Werror=implicit-function-declaration]
> > if (acpi_sleep_state_supported(ACPI_STATE_S5)) {
> > ^
> > cc1: some warnings being treated as errors
> > make[2]: *** [drivers/acpi/sleep.o] Error 1
> > make[1]: *** [drivers/acpi] Error 2
> > make: *** [drivers] Error 2
> >
> > Function is defined inside a #ifdef CONFIG_SUSPEND, but used outside of
> > one in acpi_sleep_init().
>
> This isn't caught by the build test robot. Care to submit that .config to
> Fengguang so that you don't have to report such failures again?
Sorry about that! It's because the build test robot skips compilation
for many trees due to a newly introduced bug. Have been fixed now.
Cheers,
Fengguang
next prev parent reply other threads:[~2014-03-14 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 18:48 next-20140312 - build error in drivers/acpi/sleep.c Valdis Kletnieks
2014-03-13 21:23 ` Rafael J. Wysocki
2014-03-13 22:53 ` David Rientjes
2014-03-14 0:08 ` Fengguang Wu [this message]
2014-03-14 20:56 ` Valdis.Kletnieks
2014-03-16 0:30 ` David Rientjes
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=20140314000813.GA8649@localhost \
--to=fengguang.wu@intel.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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.