[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55421B6E.4050103@de.ibm.com>
Date: Thu, 30 Apr 2015 14:09:18 +0200
From: Christian Borntraeger <borntraeger@...ibm.com>
To: Preeti U Murthy <preeti@...ux.vnet.ibm.com>
CC: peterz@...radead.org, paulmck@...ux.vnet.ibm.com,
dave@...olabs.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kernel: Replace reference to ASSIGN_ONCE with WRITE_ONCE
in comment
Am 30.04.2015 um 13:57 schrieb Preeti U Murthy:
> Looks like commit :
>
> 43239cbe79fc ("kernel: Change ASSIGN_ONCE(val, x) to WRITE_ONCE(x, val)")
>
> left behind a reference to ASSIGN_ONCE. Update this to WRITE_ONCE.
>
> Signed-off-by: Preeti U Murthy <preeti@...ux.vnet.ibm.com>
Acked-by: Christian Borntraeger <borntraeger@...ibm.com>
> ---
>
> include/linux/compiler.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/compiler.h b/include/linux/compiler.h
> index 0e41ca0..e65e0a7 100644
> --- a/include/linux/compiler.h
> +++ b/include/linux/compiler.h
> @@ -446,7 +446,7 @@ static __always_inline void __write_once_size(volatile void *p, void *res, int s
> * with an explicit memory barrier or atomic instruction that provides the
> * required ordering.
> *
> - * If possible use READ_ONCE/ASSIGN_ONCE instead.
> + * If possible use READ_ONCE/WRITE_ONCE instead.
> */
> #define __ACCESS_ONCE(x) ({ \
> __maybe_unused typeof(x) __var = (__force typeof(x)) 0; \
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists