From: Costa Shulyupin <costa.shul@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Tomas Glozar <tglozar@redhat.com>,
Ian Rogers <irogers@google.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Alexandre Chartre <alexandre.chartre@oracle.com>,
Costa Shulyupin <costa.shul@redhat.com>,
Blake Jones <blakejones@google.com>,
Yuzhuo Jing <yuzhuo@google.com>, Leo Yan <leo.yan@arm.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] tools/rtla: Add unit tests
Date: Mon, 19 Jan 2026 12:58:55 +0200 [thread overview]
Message-ID: <20260119105857.797498-1-costa.shul@redhat.com> (raw)
v2: Address feedback from Tomas Glozar
- Split the patch.
- Extract separate target unit-tests.
- Use build system
- Add libcheck to tools/build dependency detection
Costa Shulyupin (2):
tools/build: Add feature test for libcheck
tools/rtla: Add unit tests for utils.c
tools/build/Makefile.feature | 3 +
tools/build/feature/Makefile | 4 +
tools/build/feature/test-libcheck.c | 8 ++
tools/tracing/rtla/Build | 1 +
tools/tracing/rtla/Makefile | 5 +
tools/tracing/rtla/Makefile.config | 8 ++
tools/tracing/rtla/README.txt | 1 +
tools/tracing/rtla/tests/unit/Build | 2 +
tools/tracing/rtla/tests/unit/Makefile.unit | 17 +++
tools/tracing/rtla/tests/unit/unit_tests.c | 123 ++++++++++++++++++++
10 files changed, 172 insertions(+)
create mode 100644 tools/build/feature/test-libcheck.c
create mode 100644 tools/tracing/rtla/tests/unit/Build
create mode 100644 tools/tracing/rtla/tests/unit/Makefile.unit
create mode 100644 tools/tracing/rtla/tests/unit/unit_tests.c
--
2.52.0
next reply other threads:[~2026-01-19 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 10:58 Costa Shulyupin [this message]
2026-01-19 10:58 ` [PATCH v2 1/2] tools/build: Add feature test for libcheck Costa Shulyupin
2026-01-19 10:58 ` [PATCH v2 2/2] tools/rtla: Add unit tests for utils.c Costa Shulyupin
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=20260119105857.797498-1-costa.shul@redhat.com \
--to=costa.shul@redhat.com \
--cc=acme@redhat.com \
--cc=alexandre.chartre@oracle.com \
--cc=blakejones@google.com \
--cc=irogers@google.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglozar@redhat.com \
--cc=yuzhuo@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox