linux-user: fix comment s/atomic_write/atomic_set/

[Qemu-devel] [PATCH] linux-user: fix comment s/atomic_write/atomic_set/

Emilio G. Cota posted 1 patch 7 years, 2 months ago

Download mbox

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20180811211011.6277-1-cota@braap.org

Test checkpatch passed

Test docker-mingw@fedora passed

Test docker-clang@ubuntu passed

Test docker-quick@centos7 passed

linux-user/qemu.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Expand all Fold all

[Qemu-devel] [PATCH] linux-user: fix comment s/atomic_write/atomic_set/

Posted by Emilio G. Cota 7 years, 2 months ago

Signed-off-by: Emilio G. Cota <cota@braap.org>
---
 linux-user/qemu.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/linux-user/qemu.h b/linux-user/qemu.h
index b4959e41c6..e6a8bc5867 100644
--- a/linux-user/qemu.h
+++ b/linux-user/qemu.h
@@ -143,7 +143,7 @@ typedef struct TaskState {
     /* Nonzero if process_pending_signals() needs to do something (either
      * handle a pending signal or unblock signals).
      * This flag is written from a signal handler so should be accessed via
-     * the atomic_read() and atomic_write() functions. (It is not accessed
+     * the atomic_read() and atomic_set() functions. (It is not accessed
      * from multiple threads.)
      */
     int signal_pending;
-- 
2.17.1

Re: [Qemu-devel] [PATCH] linux-user: fix comment s/atomic_write/atomic_set/

Posted by Laurent Vivier 7 years ago

On 11/08/2018 22:10, Emilio G. Cota wrote:
> Signed-off-by: Emilio G. Cota <cota@braap.org>
> ---
>  linux-user/qemu.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/linux-user/qemu.h b/linux-user/qemu.h
> index b4959e41c6..e6a8bc5867 100644
> --- a/linux-user/qemu.h
> +++ b/linux-user/qemu.h
> @@ -143,7 +143,7 @@ typedef struct TaskState {
>      /* Nonzero if process_pending_signals() needs to do something (either
>       * handle a pending signal or unblock signals).
>       * This flag is written from a signal handler so should be accessed via
> -     * the atomic_read() and atomic_write() functions. (It is not accessed
> +     * the atomic_read() and atomic_set() functions. (It is not accessed
>       * from multiple threads.)
>       */
>      int signal_pending;
> 

Applied

Thanks,
Laurent