Re: [PATCH 1/2] x86_32: summit_32, use BAD_APICID

From: Ingo Molnar
Date: Tue Feb 24 2009 - 12:55:43 EST

Next message: Mel Gorman: "Re: [PATCH 08/19] Simplify the check on whether cpusets are afactor or not"
Previous message: Mel Gorman: "Re: [PATCH 10/19] Calculate the preferred zone for allocation onlyonce"
In reply to: jirislaby: "[PATCH 2/2] x86_32: summit_32, de-inline functions"
Next in thread: Jiri Slaby: "[PATCH v2 1/2] x86_32: summit_32, use BAD_APICID"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

* jirislaby@xxxxxxxxx <jirislaby@xxxxxxxxx> wrote:

> From: Jiri Slaby <jirislaby@xxxxxxxxx>
>
> Use BAD_APICID instead of 0xFF constants in summit_cpu_mask_to_apicid.
>
> Also remove bogus comments about what we actually return.

Hm, please send x86 patches against the latest x86 tree:

http://people.redhat.com/mingo/tip.git/README

the Summit code moved to another position in the tree so your
patches dont apply anymore.

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

Next message: Mel Gorman: "Re: [PATCH 08/19] Simplify the check on whether cpusets are afactor or not"
Previous message: Mel Gorman: "Re: [PATCH 10/19] Calculate the preferred zone for allocation onlyonce"
In reply to: jirislaby: "[PATCH 2/2] x86_32: summit_32, de-inline functions"
Next in thread: Jiri Slaby: "[PATCH v2 1/2] x86_32: summit_32, use BAD_APICID"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]