From: Dave Hansen <haveblue@us.ibm.com>
To: Alex Williamson <alex.williamson@hp.com>
Cc: acpi-devel <acpi-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cleanup ACPI numa warnings
Date: Thu, 05 Aug 2004 14:01:43 -0700 [thread overview]
Message-ID: <1091739702.31490.245.camel@nighthawk> (raw)
In-Reply-To: <1091738798.22406.9.camel@tdi>
On Thu, 2004-08-05 at 13:46, Alex Williamson wrote:
> +#ifdef ACPI_DEBUG_OUTPUT
> +#define acpi_print_srat_processor_affinity(header) { \
> + struct acpi_table_processor_affinity *p = \
> + (struct acpi_table_processor_affinity*) header; \
> + ACPI_DEBUG_PRINT((ACPI_DB_INFO, "SRAT Processor (id[0x%02x] " \
> + "eid[0x%02x]) in proximity domain %d %s\n", \
> + p->apic_id, p->lsapic_eid, p->proximity_domain, \
> + p->flags.enabled?"enabled":"disabled")); }
> +
> +#define acpi_print_srat_memory_affinity(header) { \
> + struct acpi_table_memory_affinity *p = \
> + (struct acpi_table_memory_affinity*) header; \
> + ACPI_DEBUG_PRINT((ACPI_DB_INFO, "SRAT Memory (0x%08x%08x length " \
> + "0x%08x%08x type 0x%x) in proximity domain %d %s%s\n",\
> + p->base_addr_hi, p->base_addr_lo, p->length_hi, \
> + p->length_lo, p->memory_type, p->proximity_domain, \
> + p->flags.enabled ? "enabled" : "disabled", \
> + p->flags.hot_pluggable ? " hot-pluggable" : "")); }
Is there a reason that this can't be a normal function instead of a
9-line #define?
-- Dave
next prev parent reply other threads:[~2004-08-05 21:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 20:46 Alex Williamson
2004-08-05 21:01 ` Dave Hansen [this message]
2004-08-05 21:25 ` Alex Williamson
2004-08-06 3:35 ` Martin J. Bligh
2004-08-06 3:50 ` [ACPI] " Randy.Dunlap
2004-08-07 17:57 ` Paul Jackson
2004-08-08 21:36 ` Randy.Dunlap
2004-08-09 2:53 ` Martin J. Bligh
2004-08-20 18:55 ` Alex Williamson
2004-08-20 19:22 ` Jesse Barnes
2004-08-09 4:19 ` Alex Williamson
2004-08-09 4:52 ` Dave Hansen
2004-08-09 5:10 ` Alex Williamson
2004-08-09 5:44 ` Dave Hansen
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=1091739702.31490.245.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=alex.williamson@hp.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
Powered by JetHome