From: "Jan Beulich" <jbeulich@novell.com>
To: "Andrew Paprocki" <andrew@ishiboo.com>,
"Andi Kleen" <ak@linux.intel.com>
Cc: <robert.moore@intel.com>, "Len Brown" <lenb@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"LKML" <linux-kernel@vger.kernel.org>
Subject: Re: ACPI WARNING: at drivers/acpi/tables/tbfadt.c:348 acpi_tb_create_local_fadt+0x147/0x2f4()
Date: Thu, 17 Jul 2008 14:58:42 +0100 [thread overview]
Message-ID: <487F6C32.76E4.0078.0@novell.com> (raw)
In-Reply-To: <76366b180807170603qaf669a5q625fc166a2045756@mail.gmail.com>
>>> "Andrew Paprocki" <andrew@ishiboo.com> 17.07.08 15:03 >>>
>On Thu, Jul 17, 2008 at 8:28 AM, Andi Kleen <ak@linux.intel.com> wrote:
>> Ok, but we can just get that from a table dump.
>
>Output from acpidump is attached.
Just as I suspected - the v1 field says 4 bytes, but the v2 field says 8 bits.
Jan
next prev parent reply other threads:[~2008-07-17 13:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 2:29 ACPI WARNING: at drivers/acpi/tables/tbfadt.c:348 acpi_tb_create_local_fadt+0x147/0x2f4() Andrew Paprocki
2008-07-17 3:34 ` Andrew Paprocki
2008-07-17 8:59 ` Jan Beulich
2008-07-17 9:06 ` Andi Kleen
2008-07-17 9:14 ` Jan Beulich
2008-07-17 12:28 ` Andi Kleen
2008-07-17 13:03 ` Andrew Paprocki
2008-07-17 13:58 ` Jan Beulich [this message]
2008-07-17 14:32 ` Andrew Paprocki
2008-07-17 15:30 ` Jan Beulich
2008-07-17 17:20 ` ACPI WARNING: at drivers/acpi/tables/tbfadt.c:348acpi_tb_create_local_fadt+0x147/0x2f4() Moore, Robert
2008-07-17 17:40 ` Andi Kleen
2008-07-18 7:53 ` Jan Beulich
2008-07-18 8:43 ` Jan Beulich
2008-07-18 16:52 ` ACPI WARNING: atdrivers/acpi/tables/tbfadt.c:348acpi_tb_create_local_fadt+0x147/0x2f4() Moore, Robert
2008-07-18 9:48 ` ACPI WARNING: at drivers/acpi/tables/tbfadt.c:348acpi_tb_create_local_fadt+0x147/0x2f4() Jan Beulich
2008-07-17 9:00 ` ACPI WARNING: at drivers/acpi/tables/tbfadt.c:348 acpi_tb_create_local_fadt+0x147/0x2f4() Andi Kleen
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=487F6C32.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrew@ishiboo.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.moore@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.