Re: [RFC][PATCH 2/9] conditionally define generic get_order() (ARCH_HAS_GET_ORDER)

On 8/31/06, Dave Hansen <[email protected]> wrote:

diff -puN mm/Kconfig~generic-get_order mm/Kconfig
--- threadalloc/mm/Kconfig~generic-get_order    2006-08-30 15:14:56.000000000 -0700
+++ threadalloc-dave/mm/Kconfig 2006-08-30 15:15:00.000000000 -0700
@@ -1,3 +1,7 @@
+config ARCH_HAVE_GET_ORDER
+       def_bool y
+       depends on IA64 || PPC32 || XTENSA
+

I have a feeling this has been discussed before, but wouldn't it be
better to let each architecture define this in its own Kconfig?

At some point, I have to add AVR32 to that list, and if one or more
other architectures need to do the same, there will be rejects.

Haavard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC][PATCH 2/9] conditionally define generic get_order() (ARCH_HAS_GET_ORDER)
    • From: Dave Hansen <[email protected]>

• References:
  • [RFC][PATCH 0/9] generic PAGE_SIZE infrastructure (v4)
    • From: Dave Hansen <[email protected]>
  • [RFC][PATCH 2/9] conditionally define generic get_order() (ARCH_HAS_GET_ORDER)
    • From: Dave Hansen <[email protected]>

• Prev by Date: Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
• Next by Date: [PATCH] Change return value from schedule_work()
• Previous by thread: [RFC][PATCH 2/9] conditionally define generic get_order() (ARCH_HAS_GET_ORDER)
• Next by thread: Re: [RFC][PATCH 2/9] conditionally define generic get_order() (ARCH_HAS_GET_ORDER)
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]