Messages in this thread Patch in this message | | | From | Rasmus Villemoes <> | Subject | [PATCH resend] linux/compiler.h: fix stale comment on {READ,WRITE}_ONCE | Date | Thu, 10 Mar 2016 01:16:57 +0100 |
| |
Commit 7bd3e239d6c6 ("locking: Remove atomicy checks from {READ,WRITE}_ONCE") removed said warning.
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk> --- Andrew, can you pick this up please?
include/linux/compiler.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/linux/compiler.h b/include/linux/compiler.h index 48f5aab117ae..062b6ad95276 100644 --- a/include/linux/compiler.h +++ b/include/linux/compiler.h @@ -263,8 +263,7 @@ static __always_inline void __write_once_size(volatile void *p, void *res, int s * In contrast to ACCESS_ONCE these two macros will also work on aggregate * data types like structs or unions. If the size of the accessed data * type exceeds the word size of the machine (e.g., 32 bits or 64 bits) - * READ_ONCE() and WRITE_ONCE() will fall back to memcpy and print a - * compile-time warning. + * READ_ONCE() and WRITE_ONCE() will fall back to memcpy. * * Their two major use cases are: (1) Mediating communication between * process-level code and irq/NMI handlers, all running on the same CPU, -- 2.1.4
| |