[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200809250901.09212.bjorn.helgaas@hp.com>
Date: Thu, 25 Sep 2008 09:01:08 -0600
From: Bjorn Helgaas <bjorn.helgaas@...com>
To: Yinghai Lu <yhlu.kernel@...il.com>
Cc: Jesse Barnes <jbarnes@...tuousgeek.org>,
Len Brown <lenb@...nel.org>, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
linux-acpi@...r.kernel.org
Subject: Re: [PATCH 2/7] acpi: remove have_arch_parse_srat in acpi.h
On Wednesday 24 September 2008 08:04:32 pm Yinghai Lu wrote:
> 32bit don't need that anymore
I don't understand the connection between this commit log and
the patch below.
> Signed-off-by: Yinghai Lu <yhlu.kernel@...il.com>
> ---
> include/linux/acpi.h | 8 --------
> 1 files changed, 0 insertions(+), 8 deletions(-)
>
> diff --git a/include/linux/acpi.h b/include/linux/acpi.h
> index 4d5ec43..8eefaa9 100644
> --- a/include/linux/acpi.h
> +++ b/include/linux/acpi.h
> @@ -95,18 +95,10 @@ int acpi_parse_mcfg (struct acpi_table_header *header);
> void acpi_table_print_madt_entry (struct acpi_subtable_header *madt);
>
> /* the following four functions are architecture-dependent */
> -#ifdef CONFIG_HAVE_ARCH_PARSE_SRAT
> -#define NR_NODE_MEMBLKS MAX_NUMNODES
> -#define acpi_numa_slit_init(slit) do {} while (0)
> -#define acpi_numa_processor_affinity_init(pa) do {} while (0)
> -#define acpi_numa_memory_affinity_init(ma) do {} while (0)
> -#define acpi_numa_arch_fixup() do {} while (0)
> -#else
> void acpi_numa_slit_init (struct acpi_table_slit *slit);
> void acpi_numa_processor_affinity_init (struct acpi_srat_cpu_affinity *pa);
> void acpi_numa_memory_affinity_init (struct acpi_srat_mem_affinity *ma);
> void acpi_numa_arch_fixup(void);
> -#endif
>
> #ifdef CONFIG_ACPI_HOTPLUG_CPU
> /* Arch dependent functions for cpu hotplug support */
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists