On Thu, Nov 15, 2007 at 07:21:51AM -0500, Mathieu Desnoyers wrote:
>
> FWIW, I've used "NEED_*" in my LTTng patchset to specify when an
> architecture needs support from an architecture independent module. (it
> could be an alternative to USE_*).
The situations we need to cover are:
1) An architecture uses or support a generic implementation
Examples: KPROBES, GENERIC_TIME
2) An architecture uses a specific functionality
Examples: MMU
3) Architecture provide a specific functionality
Examples: ARCH_HAS_ILOG2_U32, ARCH_HAS_ILOG2_U64
4) A driver is supported by a subset of the architectures
Example: config EDAC
depends on X86 || PPC
I'm very tempted to go with the suggestion of Russell and
say that the naming is the very generic:
HAVE_<config-symbol>
We know it from the auto-tools (albeit that could be a reason to avoid it)
And we can hardly put wrong interpretations in the HAVE_ thing.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
