public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: Andrew Morton <akpm@osdl.org>
Cc: bunk@stusta.de, reuben-lkml@reub.net, len.brown@intel.com,
	linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: 2.6.12-rc2-mm1: ACPI=y, ACPI_BOOT=n problems
Date: Wed, 06 Apr 2005 08:00:09 -0600	[thread overview]
Message-ID: <4253EB69.6050702@mesatop.com> (raw)
In-Reply-To: <20050405183655.0c778129.akpm@osdl.org>

Andrew Morton wrote:
> Steven Cole <elenstev@mesatop.com> wrote:
> 
>>arch/i386/kernel/setup.c: In function 'setup_arch':
>> arch/i386/kernel/setup.c:1571: warning: implicit declaration of function 'acpi_boot_table_init'
>> arch/i386/kernel/setup.c:1572: warning: implicit declaration of function 'acpi_boot_init'
> 
> 
> 
> diff -puN include/linux/acpi.h~no-acpi-build-fix include/linux/acpi.h
> --- 25/include/linux/acpi.h~no-acpi-build-fix	2005-04-05 00:14:46.000000000 -0700
> +++ 25-akpm/include/linux/acpi.h	2005-04-05 00:23:39.000000000 -0700
> @@ -418,16 +418,6 @@ extern int sbf_port ;
[patch snipped]

Yes, that worked with no CONFIG_ACPI.  Thanks.

On a slightly offtopic note, I'm now using this gcc:
gcc (GCC) 4.0.0 20050308 (Red Hat 4.0.0-0.32)

I don't have any quantitative data at hand, this seems SLOOOOW.
I guess that's progress.  But it slows down testing somewhat.

Steven

  reply	other threads:[~2005-04-06 14:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.gcqu6i7.1o6qrhn@ifi.uio.no>
2005-04-05  8:34 ` 2.6.12-rc2-mm1 Reuben Farrelly
2005-04-05 12:14   ` 2.6.12-rc2-mm1 Adrian Bunk
2005-04-05 12:32     ` 2.6.12-rc2-mm1 Reuben Farrelly
2005-04-05 13:24       ` 2.6.12-rc2-mm1: ACPI=y, ACPI_BOOT=n problems Adrian Bunk
2005-04-05 20:09         ` Steven Cole
2005-04-06  1:36           ` Andrew Morton
2005-04-06 14:00             ` Steven Cole [this message]
2005-04-06 21:15               ` Andrew Morton
2005-04-06  7:01 Brown, Len

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=4253EB69.6050702@mesatop.com \
    --to=elenstev@mesatop.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reuben-lkml@reub.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox