From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Len Brown <lenb@kernel.org>
Cc: sfi-devel@simplefirmware.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: sfi tree build failure
Date: Tue, 7 Jul 2009 15:43:53 +1000 [thread overview]
Message-ID: <20090707154353.628365ac.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LFD.2.00.0907062348130.32467@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
Hi Len,
On Tue, 07 Jul 2009 00:01:13 -0400 (EDT) Len Brown <lenb@kernel.org> wrote:
>
> > On Tue, 30 Jun 2009 17:19:37 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > Today's linux-next build (powerpc ppc64_defconfig) failed like this:
> > >
> > > In file included from include/acpi/platform/acenv.h:141,
> > > from include/acpi/acpi.h:56,
> > > from include/linux/acpi.h:38,
> > > from init/main.c:27:
> > > include/acpi/platform/aclinux.h:64:22: error: asm/acpi.h: No such file or directory
> ...
> > > I have dropped the sfi tree for today.
> >
> > And the sfi tree has still not made it into linux-next as the above error
> > still exists.
>
> Sorry about breaking the PPC build, Stephen.
>
> I screwed up in my hack attempt to support CONFIG_SFI=y && CONFIG_ACPI=n.
>
> Let me know if you have any trouble with the latest SFI test tree.
I still get the same error. Note that asm/acpi.h is being included from
include/acpi/platform/aclinux.h
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-07-07 5:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 7:19 linux-next: sfi tree build failure Stephen Rothwell
2009-07-06 6:14 ` Stephen Rothwell
2009-07-07 4:01 ` Len Brown
2009-07-07 4:13 ` Stephen Rothwell
2009-07-07 5:43 ` Stephen Rothwell [this message]
2009-07-07 15:31 ` Len Brown
2009-07-08 0:50 ` Stephen Rothwell
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=20090707154353.628365ac.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfi-devel@simplefirmware.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