From: Daniel Vetter <daniel@ffwll•ch>
To: "Rafael J. Wysocki" <rjw@rjwysocki•net>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Randy Dunlap <rdunlap@infradead•org>,
Daniel Vetter <daniel.vetter@ffwll•ch>,
intel-gfx <intel-gfx@lists•freedesktop.org>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel•com>,
linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
dri-devel <dri-devel@lists•freedesktop.org>
Subject: Re: linux-next: Tree for Jun 19 (drm/i915)
Date: Mon, 7 Jul 2014 22:06:59 +0200 [thread overview]
Message-ID: <20140707200659.GL5821@phenom.ffwll.local> (raw)
In-Reply-To: <16952236.GFHaOHoKy4@vostro.rjw.lan>
On Mon, Jul 07, 2014 at 10:01:27PM +0200, Rafael J. Wysocki wrote:
> On Monday, July 07, 2014 04:54:23 PM Daniel Vetter wrote:
> > On Wed, Jun 25, 2014 at 01:01:36AM +0200, Rafael J. Wysocki wrote:
> > > On Tuesday, June 24, 2014 02:43:02 PM Jani Nikula wrote:
> > > > On Thu, 19 Jun 2014, Randy Dunlap <rdunlap@infradead•org> wrote:
> > > > > 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
> > > >
> > > > Thanks for the report, we'll fix it.
> > > >
> > > > Can anyone explain why include/linux/acpi_bus.h has #ifdef
> > > > CONFIG_ACPI_SLEEP and conditional build for a dummy inline version of
> > > > acpi_target_system_state(), *but* that does not get included or used if
> > > > CONFIG_ACPI=n? Additionally, the combination of CONFIG_ACPI=y and
> > > > CONFIG_ACPI_SLEEP=n does not seem to work at all.
> > >
> > > These two things look like bugs to me. Most likely not tested thoruoughly
> > > enough.
> > >
> > > > So we'll really have to sprinkle #ifdef CONFIG_ACPI all over, instead of
> > > > neatly using the dummy versions that someone has gone through the
> > > > trouble of adding?
> > >
> > > No, we don't have to.
> >
> > Back from my vacation and I didn't see a conclusion to this issue here.
> > Rafael, have you fixed this in your acpi tree or do I need to do something
> > in drm-intel?
>
> I was on vacation too. :-)
>
> Please have a look if i915 includes acpi/acpi_bus.h directly anywhere. If so,
> it should include linux/acpi.h instead. I'll fix up the rest in the ACPI tree.
We seem to only use linux/acpi.h and acpi/(video|button).h, at least
according to a grep include.*acpi. So I think we're good in i915 land.
Thanks for taking care of this.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-07-07 20:06 UTC|newest]
Thread overview: 11+ 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 ` linux-next: Tree for Jun 19 (drm/i915) Randy Dunlap
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:06 ` Daniel Vetter [this message]
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=20140707200659.GL5821@phenom.ffwll.local \
--to=daniel@ffwll$(echo .)ch \
--cc=daniel.vetter@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rafael.j.wysocki@intel$(echo .)com \
--cc=rdunlap@infradead$(echo .)org \
--cc=rjw@rjwysocki$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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