From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/2] tst_atomic: drop legacy inline assembly and use __atomic or __sync builtins
Date: Fri, 6 Jun 2025 12:16:09 +0200 [thread overview]
Message-ID: <aEK_6WPCvW8abU-F@yuki.lan> (raw)
In-Reply-To: <CAEemH2cVpKAh3aPOzz82Cbvik_gQzpzySu7SsoTePTvKtGZkOA@mail.gmail.com>
Hi!
> Or, do you think it's necessary to define a dedicated tst_atomic_t type,
> such as:
> typedef int32_t tst_atomic_t;
> and use it explicitly for all variables that are subject to atomic
> operations?
>
> This way, we can clearly declare which values are intended for atomic use,
> improving type safety and code clarity.
Sounds good to me.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2025-06-06 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 12:07 [LTP] [PATCH v2 1/2] tst_atomic: drop legacy inline assembly and use __atomic or __sync builtins Li Wang via ltp
2025-06-05 12:07 ` [LTP] [PATCH v2 2/2] lib: moves test infrastructure states into a shared context structure Li Wang via ltp
2025-06-05 12:20 ` Li Wang via ltp
2025-06-06 9:18 ` [LTP] [PATCH v2 1/2] tst_atomic: drop legacy inline assembly and use __atomic or __sync builtins Cyril Hrubis
2025-06-06 9:36 ` Li Wang via ltp
2025-06-06 10:10 ` Li Wang via ltp
2025-06-06 10:16 ` Cyril Hrubis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aEK_6WPCvW8abU-F@yuki.lan \
--to=chrubis@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.