> Thus, any reliance on type-qualifying an object that represents an atomic > or locking primitive on the keyword 'volatile' is misplaced. arch/foo is generally implementation specific code. - 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] doc: volatile considered evil
- From: David Rientjes <[email protected]>
- Re: [PATCH] doc: volatile considered evil
- References:
- [RFC, PATCH 2/4] SoC base drivers: ASIC3 SoC hardware definitions
- From: Paul Sokolovsky <[email protected]>
- Re: [RFC, PATCH 2/4] SoC base drivers: ASIC3 SoC hardware definitions
- From: Andrew Morton <[email protected]>
- [RFC/PATCH] doc: volatile considered evil
- From: Randy Dunlap <[email protected]>
- Re: [RFC/PATCH] doc: volatile considered evil
- From: "Satyam Sharma" <[email protected]>
- [PATCH] doc: volatile considered evil
- From: Randy Dunlap <[email protected]>
- Re: [PATCH] doc: volatile considered evil
- From: David Rientjes <[email protected]>
- Re: [PATCH] doc: volatile considered evil
- From: Randy Dunlap <[email protected]>
- Re: [PATCH] doc: volatile considered evil
- From: David Rientjes <[email protected]>
- Re: [PATCH] doc: volatile considered evil
- From: Alan Cox <[email protected]>
- Re: [PATCH] doc: volatile considered evil
- From: David Rientjes <[email protected]>
- [RFC, PATCH 2/4] SoC base drivers: ASIC3 SoC hardware definitions
- Prev by Date: Re: [linux-usb-devel] Bug creating USB endpoints in 2.6.20.x (kernel bug 8198)
- Next by Date: Re: Please revert 5adc55da4a7758021bcc374904b0f8b076508a11 (PCI_MULTITHREAD_PROBE)
- Previous by thread: Re: [PATCH] doc: volatile considered evil
- Next by thread: Re: [PATCH] doc: volatile considered evil
- Index(es):
 |