"Bryan O'Sullivan" <[email protected]> wrote: > > OK, that header file will vanish. > It's kinda fun playing Brian along like this ;) One option is to just stick the thing in an existing lib/ or kernel/ file and mark it __attribute__((weak)). That way architectures can override it for free with no ifdefs, no Makefile trickery, no Kconfig trickery, etc. attribute(weak) is creepily useful - I keep waiting for something to go wrong with it. - 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: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- From: "Bryan O'Sullivan" <[email protected]>
- Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- References:
- [PATCH 0 of 3] 32-bit MMIO copy routine
- From: "Bryan O'Sullivan" <[email protected]>
- [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- From: "Bryan O'Sullivan" <[email protected]>
- Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- From: Andrew Morton <[email protected]>
- Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- From: Roland Dreier <[email protected]>
- Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- From: "Bryan O'Sullivan" <[email protected]>
- Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- From: Christoph Hellwig <[email protected]>
- Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- From: "Bryan O'Sullivan" <[email protected]>
- Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- From: Christoph Hellwig <[email protected]>
- Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- From: "Bryan O'Sullivan" <[email protected]>
- [PATCH 0 of 3] 32-bit MMIO copy routine
- Prev by Date: ntohs/ntohl and bitops
- Next by Date: Re: Although CONFIG_IRQBALANCE is enabled IRQ's don't seem to be balanced very well
- Previous by thread: Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- Next by thread: Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- Index(es):
 |