From: Alex Hung <alex.hung@amd.com>
To: <richard@nod.at>, <anton.ivanov@cambridgegreys.com>,
<johannes@sipsolutions.net>, <nathan@kernel.org>,
<linux-um@lists.infradead.org>
Cc: <alex.hung@amd.com>
Subject: [PATCH 0/1][RFC] Fix no gcda files with kunit.py
Date: Tue, 12 May 2026 17:26:39 -0600 [thread overview]
Message-ID: <20260512232640.1937941-1-alex.hung@amd.com> (raw)
This patch is generated by Claude Sonnet and it is outside my knowledge
domain. Any comments or solutions are appreciated.
Command: CC="ccache gcc" ./tools/testing/kunit/kunit.py run --kunitconfig drivers/gpu/drm/amd/display/amdgpu_dm/tests/.kunitconfig
Without this patch, the error messages is shown with some WIP kunit
patches by lcov command:
Found gcov version: 13.3.0
Using intermediate gcov format
Writing temporary data to /tmp/geninfo_dat9yJO
Scanning .kunit/drivers/gpu/drm/amd/display/amdgpu_dm for .gcda files ...
geninfo: ERROR: no .gcda files found in .kunit/drivers/gpu/drm/amd/display/amdgpu_dm\
...
With this fix, it shows
Found gcov version: 13.3.0
Using intermediate gcov format
Writing temporary data to /tmp/geninfo_datLqI9
Scanning .kunit/drivers/gpu/drm/amd/display/amdgpu_dm for .gcda files ...
Found 25 data files in .kunit/drivers/gpu/drm/amd/display/amdgpu_dm
Processing .kunit/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_psr.gcda
...
Alex Hung (1):
um: include .fini_array.* in linker scripts
arch/um/include/asm/common.lds.S | 1 +
arch/um/kernel/dyn.lds.S | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2026-05-12 23:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 23:26 Alex Hung [this message]
2026-05-12 23:26 ` [PATCH 1/1[RFC] um: include .fini_array.* in linker scripts Alex Hung
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=20260512232640.1937941-1-alex.hung@amd.com \
--to=alex.hung@amd.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=nathan@kernel.org \
--cc=richard@nod.at \
/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