From: Marcus Hartig <m.f.h@web.de>
To: Len Brown <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BKPATCH] ACPI for 2.6
Date: Sun, 15 Aug 2004 18:58:11 +0200 [thread overview]
Message-ID: <1092589091.3806.10.camel@redtuxi> (raw)
In-Reply-To: <1092509038.7765.271.camel@dhcppc4>
Len Brown wrote:
> Hmm, this config builds for me with gcc 3.3,
> and neither dsfield.c nor acnamesp.h have changed in months.
>
> is it possible your source tree has been corrupted?
Yes, my kernel source tree was corrupted... Do not know why.
Now, with 2.6.8.1 and the ACPI patch no problems with my nForce2 board.
Thanks,
Marcus
--
www.marcush.de
next prev parent reply other threads:[~2004-08-15 16:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <566B962EB122634D86E6EE29E83DD808182C3286@hdsmsx403.hd.intel.com>
2004-08-14 18:43 ` [BKPATCH] ACPI for 2.6 Len Brown
2004-08-15 16:58 ` Marcus Hartig [this message]
2004-11-09 7:47 Len Brown
2004-11-12 17:42 ` Pavel Machek
2004-12-01 23:13 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2004-10-09 5:54 Len Brown
2004-08-14 23:08 Len Brown
2004-08-14 16:40 Marcus Hartig
2004-08-14 6:55 Len Brown
2004-08-14 20:56 ` Jesse Barnes
2004-06-21 19:41 Len Brown
2004-06-18 6:42 Len Brown
2004-05-20 19:12 Len Brown
2004-05-11 16:48 Len Brown
2004-05-03 16:52 Len Brown
2004-04-01 10:40 Len Brown
2004-03-27 0:59 Len Brown
2004-03-27 11:11 ` Marcel Holtmann
2004-03-23 10:02 Len Brown
2004-03-14 6:08 Len Brown
2004-03-06 6:37 Len Brown
2004-02-25 9:18 Len Brown
2004-02-14 4:46 Len Brown
2004-02-07 9:10 Len Brown
2004-02-09 9:09 ` Olaf Hering
2004-02-09 9:11 ` Olaf Hering
2004-01-27 6:03 Len Brown
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=1092589091.3806.10.camel@redtuxi \
--to=m.f.h@web.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.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