[PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2008-01-08 Thread travis
The use of the __GENERIC_PERCPU is a bit problematic since arches may want to run their own percpu setup while using the generic percpu definitions. Replace it through a kconfig variable. Cc: Rusty Russell <[EMAIL PROTECTED]> Cc: Andi Kleen <[EMAIL PROTECTED]> Cc: Sam Ravnborg <[EMAIL PROTECTED]>

Re: [PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2008-01-08 Thread Sam Ravnborg
On Mon, Jan 07, 2008 at 06:11:43PM -0800, [EMAIL PROTECTED] wrote: > V1->V2: > - Use def_bool as suggested by Randy. > > The use of the __GENERIC_PERCPU is a bit problematic since arches > may want to run their own percpu setup while using the generic > percpu definitions. Replace it through a

Re: [PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2008-01-08 Thread Sam Ravnborg
On Mon, Jan 07, 2008 at 06:11:43PM -0800, [EMAIL PROTECTED] wrote: V1-V2: - Use def_bool as suggested by Randy. The use of the __GENERIC_PERCPU is a bit problematic since arches may want to run their own percpu setup while using the generic percpu definitions. Replace it through a kconfig

[PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2008-01-08 Thread travis
The use of the __GENERIC_PERCPU is a bit problematic since arches may want to run their own percpu setup while using the generic percpu definitions. Replace it through a kconfig variable. Cc: Rusty Russell [EMAIL PROTECTED] Cc: Andi Kleen [EMAIL PROTECTED] Cc: Sam Ravnborg [EMAIL PROTECTED]

[PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2008-01-07 Thread travis
V1->V2: - Use def_bool as suggested by Randy. The use of the __GENERIC_PERCPU is a bit problematic since arches may want to run their own percpu setup while using the generic percpu definitions. Replace it through a kconfig variable. Cc: Rusty Russell <[EMAIL PROTECTED]> Cc: Andi Kleen <[EMAIL

[PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2008-01-07 Thread travis
V1-V2: - Use def_bool as suggested by Randy. The use of the __GENERIC_PERCPU is a bit problematic since arches may want to run their own percpu setup while using the generic percpu definitions. Replace it through a kconfig variable. Cc: Rusty Russell [EMAIL PROTECTED] Cc: Andi Kleen [EMAIL

[PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2007-12-27 Thread travis
V1->V2: - Use def_bool as suggested by Randy. The use of the __GENERIC_PERCPU is a bit problematic since arches may want to run their own percpu setup while using the generic percpu definitions. Replace it through a kconfig variable. Cc: Rusty Russell <[EMAIL PROTECTED]> Cc: Andi Kleen <[EMAIL

Re: [PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2007-12-27 Thread David Miller
From: [EMAIL PROTECTED] Date: Thu, 27 Dec 2007 16:10:47 -0800 > V1->V2: > - Use def_bool as suggested by Randy. > > The use of the __GENERIC_PERCPU is a bit problematic since arches > may want to run their own percpu setup while using the generic > percpu definitions. Replace it through a

[PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2007-12-27 Thread travis
V1->V2: - Use def_bool as suggested by Randy. The use of the __GENERIC_PERCPU is a bit problematic since arches may want to run their own percpu setup while using the generic percpu definitions. Replace it through a kconfig variable. Cc: Rusty Russell <[EMAIL PROTECTED]> Cc: Andi Kleen <[EMAIL

[PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2007-12-27 Thread travis
V1-V2: - Use def_bool as suggested by Randy. The use of the __GENERIC_PERCPU is a bit problematic since arches may want to run their own percpu setup while using the generic percpu definitions. Replace it through a kconfig variable. Cc: Rusty Russell [EMAIL PROTECTED] Cc: Andi Kleen [EMAIL

Re: [PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2007-12-27 Thread David Miller
From: [EMAIL PROTECTED] Date: Thu, 27 Dec 2007 16:10:47 -0800 V1-V2: - Use def_bool as suggested by Randy. The use of the __GENERIC_PERCPU is a bit problematic since arches may want to run their own percpu setup while using the generic percpu definitions. Replace it through a kconfig

[PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2007-12-27 Thread travis
V1-V2: - Use def_bool as suggested by Randy. The use of the __GENERIC_PERCPU is a bit problematic since arches may want to run their own percpu setup while using the generic percpu definitions. Replace it through a kconfig variable. Cc: Rusty Russell [EMAIL PROTECTED] Cc: Andi Kleen [EMAIL

[patch 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2007-11-28 Thread Christoph Lameter
V1->V2: - Use def_bool as suggested by Randy. The use of the __GENERIC_PERCPU is a bit problematic since arches may want to run their own percpu setup while using the generic percpu definitions. Replace it through a kconfig variable. Cc: Rusty Russell <[EMAIL PROTECTED]> Cc: Andi Kleen <[EMAIL

[patch 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup

2007-11-28 Thread Christoph Lameter
V1-V2: - Use def_bool as suggested by Randy. The use of the __GENERIC_PERCPU is a bit problematic since arches may want to run their own percpu setup while using the generic percpu definitions. Replace it through a kconfig variable. Cc: Rusty Russell [EMAIL PROTECTED] Cc: Andi Kleen [EMAIL