From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/3] refine the MIN/MAX macros
Date: Fri, 11 Mar 2022 13:46:00 +0800 [thread overview]
Message-ID: <20220311054603.57328-1-liwang@redhat.com> (raw)
Add type checking to MIN/MAX and make use of them for both
new and old testcases.
Li Wang (3):
include: replace min/max macro by the new definition
lib: adding unnecessary pointer comparison
minmax: ensure the comparison numbers have compatible type
include/ipcmsg.h | 2 --
include/libnewipc.h | 1 -
include/tst_minmax.h | 2 ++
lib/tst_cgroup.c | 2 +-
lib/tst_memutils.c | 4 ++--
lib/tst_timer_test.c | 4 ++--
testcases/kernel/mem/mmapstress/mmapstress01.c | 3 +--
testcases/kernel/mem/mmapstress/mmapstress09.c | 1 -
testcases/kernel/mem/mmapstress/mmapstress10.c | 3 +--
testcases/kernel/security/cap_bound/cap_bounds_r.c | 3 +--
testcases/kernel/security/cap_bound/cap_bounds_rw.c | 7 +++----
testcases/kernel/syscalls/fallocate/fallocate06.c | 2 +-
testcases/kernel/syscalls/ipc/msgstress/msgstress01.c | 2 +-
testcases/kernel/syscalls/ipc/msgstress/msgstress02.c | 2 +-
14 files changed, 16 insertions(+), 22 deletions(-)
--
2.31.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2022-03-11 5:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 5:46 Li Wang [this message]
2022-03-11 5:46 ` [LTP] [PATCH 1/3] include: replace min/max macro by the new definition Li Wang
2022-03-23 10:19 ` Petr Vorel
2022-03-24 2:52 ` Li Wang
2022-03-11 5:46 ` [LTP] [PATCH 2/3] lib: adding unnecessary pointer comparison Li Wang
2022-03-23 10:22 ` Petr Vorel
2022-03-11 5:46 ` [LTP] [PATCH 3/3] minmax: ensure the comparison numbers have compatible type Li Wang
2022-03-11 8:52 ` Li Wang
2022-03-23 13:33 ` Petr Vorel
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=20220311054603.57328-1-liwang@redhat.com \
--to=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.