From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: Tree for Jun 19 (drm/i915)
Date: Thu, 19 Jun 2014 10:24:42 -0700 [thread overview]
Message-ID: <53A31CDA.20207@infradead.org> (raw)
In-Reply-To: <20140619161632.58b442e4@canb.auug.org.au>
On 06/18/14 23:16, Stephen Rothwell wrote:
> Hi all,
>
> The powerpc allyesconfig is again broken more than usual.
>
> Changes since 20140618:
>
on i386:
CONFIG_ACPI is not enabled.
CC drivers/gpu/drm/i915/i915_drv.o
../drivers/gpu/drm/i915/i915_drv.c: In function 'i915_drm_freeze':
../drivers/gpu/drm/i915/i915_drv.c:547:2: error: implicit declaration of function 'acpi_target_system_state' [-Werror=implicit-function-declaration]
../drivers/gpu/drm/i915/i915_drv.c:547:36: error: 'ACPI_STATE_S3' undeclared (first use in this function)
../drivers/gpu/drm/i915/i915_drv.c:547:36: note: each undeclared identifier is reported only once for each function it appears in
CC net/dccp/qpolicy.o
cc1: some warnings being treated as errors
make[5]: *** [drivers/gpu/drm/i915/i915_drv.o] Error 1
--
~Randy
next prev parent reply other threads:[~2014-06-19 17:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 6:16 linux-next: Tree for Jun 19 Stephen Rothwell
2014-06-19 17:15 ` linux-next: Tree for Jun 19 (vhost_scsi) Randy Dunlap
2014-06-19 18:22 ` Michael S. Tsirkin
2014-06-19 17:24 ` Randy Dunlap [this message]
2014-06-24 11:43 ` linux-next: Tree for Jun 19 (drm/i915) Jani Nikula
2014-06-24 11:43 ` Jani Nikula
2014-06-24 23:01 ` Rafael J. Wysocki
2014-07-07 14:54 ` Daniel Vetter
2014-07-07 20:01 ` Rafael J. Wysocki
2014-07-07 20:01 ` Rafael J. Wysocki
2014-07-07 20:06 ` Daniel Vetter
2014-07-07 20:06 ` Daniel Vetter
2014-07-07 21:49 ` Rafael J. Wysocki
2014-07-07 21:49 ` Rafael J. Wysocki
2014-07-07 23:58 ` Rafael J. Wysocki
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=53A31CDA.20207@infradead.org \
--to=rdunlap@infradead.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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.