From: Julian Braha <julianbraha@gmail.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: gor@linux.ibm.com, hca@linux.ibm.com, iii@linux.ibm.com,
meted@linux.ibm.com, borntraeger@linux.ibm.com,
svens@linux.ibm.com, akpm@linux-foundation.org,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] s390: fix dead defaults for S390_MODULES_SANITY_TEST and S390_UNWIND_SELFTEST
Date: Wed, 6 May 2026 17:51:19 +0100 [thread overview]
Message-ID: <cffeec5e-068c-4562-98ef-f65e346dff3c@gmail.com> (raw)
In-Reply-To: <3ec20142-09d1-436f-a623-21a2440ef7f0-agordeev@linux.ibm.com>
On 5/6/26 13:37, Alexander Gordeev wrote:
> In the end of the day I see no impact on the end result (aka the
> generated config) - please correct me if I am wrong.
Yes, there is actually an impact on the end result / the generated
config:
When a user of the kernel build system (e.g. 'make menuconfig') enables
the config option KUNIT_ALL_TESTS, the user expects *all of the tests*
to be enabled. Which is what commit
25d36a85c61b ("s390/test_unwind: convert to KUnit")
was attempting to do with these tests, but it appears they made a
copy-paste mistake. This is the commit referenced in the Fixes tag.
The point is, these tests were intended to be included with
KUNIT_ALL_TESTS, but aren't. This is unintended behavior, and the
definition of a bug in the kernel configuration spec.
That being said, I do agree with you that this is pretty low in
severity, as far as bugs go. It is kunit tests we're talking about,
after all. I'll check with Greg to see if he thinks this is worthy of
a Fixes tag. Another, similar patch I sent out includes the Fixes tag,
and has not received any objections from its 3 reviewers and testers
so far:
https://lore.kernel.org/all/20260405161545.161006-1-julianbraha@gmail.com/
> I think once the tool is officially included you could refer to it
> in the commit message,
I will also check on the best practices for tool-assisted development.
In the past, I have received encouragement for acknowledging the tool:
https://lore.kernel.org/all/bfdfdb05-77e2-455d-b68d-9da3fd9d1c0d@lucifer.local/
and the official kernel docs require an acknowledgement for AI tool
assistance (although this tool is not AI and doesn't generate code...)
- Julian Braha
prev parent reply other threads:[~2026-05-06 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 21:56 [RESEND PATCH] s390: fix dead defaults for S390_MODULES_SANITY_TEST and S390_UNWIND_SELFTEST Julian Braha
2026-04-29 14:42 ` Alexander Gordeev
2026-04-29 21:39 ` Julian Braha
2026-05-06 12:37 ` Alexander Gordeev
2026-05-06 16:51 ` Julian Braha [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=cffeec5e-068c-4562-98ef-f65e346dff3c@gmail.com \
--to=julianbraha@gmail.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=meted@linux.ibm.com \
--cc=svens@linux.ibm.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