From: Peter Johanson <latexer@gentoo.org>
To: Matthew Vaughn <accipiter@adelphia.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] 2.6.0-test4-mm5 breaks at drivers/acpi/pci_link.c
Date: Fri, 5 Sep 2003 08:20:15 -0700 [thread overview]
Message-ID: <20030905152015.GA10438@butchy.localhost> (raw)
In-Reply-To: <3F58A7F6.3050407@adelphia.net>
On Fri, Sep 05, 2003 at 11:12:54AM -0400, Matthew Vaughn wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In 2.6.0-test4-mm5, when CONFIG_ACPI_DEBUG=y, this happens:
>
> root@omega linux-beta # make && make modules_install
> make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
> ~ CHK include/linux/compile.h
> ~ CC drivers/acpi/pci_link.o
> drivers/acpi/pci_link.c: In function `acpi_pci_link_try_get_current':
> drivers/acpi/pci_link.c:290: `_dbg' undeclared (first use in this function)
> drivers/acpi/pci_link.c:290: (Each undeclared identifier is reported
> only once
> drivers/acpi/pci_link.c:290: for each function it appears in.)
> make[2]: *** [drivers/acpi/pci_link.o] Error 1
> make[1]: *** [drivers/acpi] Error 2
> make: *** [drivers] Error 2
>
> Is this a known bug? If not, to whom should I report it?
check out: http://lkml.org/lkml/2003/9/3/480
if you're gonna test mm-, development-, etc, i recommend highly that you
haunt one of the LKML achives first looking for fixes.. most ones like
this are picked up and reported quickly there. (part of the reason we
don't officially support these kernels, moving target and all).
-pete
--
Peter Johanson
<latexer@gentoo.org>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-09-05 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 15:12 [gentoo-dev] 2.6.0-test4-mm5 breaks at drivers/acpi/pci_link.c Matthew Vaughn
2003-09-05 15:20 ` Peter Johanson [this message]
2003-09-05 15:34 ` Mike Frysinger
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=20030905152015.GA10438@butchy.localhost \
--to=latexer@gentoo.org \
--cc=accipiter@adelphia.net \
--cc=gentoo-dev@gentoo.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