From: Heiko Carstens <hca@linux.ibm.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: linux-s390@vger.kernel.org
Subject: [PATCH 0/2] s390/char: Enable CONTEXT_ANALYSIS
Date: Thu, 6 Aug 2026 17:53:01 +0200 [thread overview]
Message-ID: <20260806155303.2675932-1-hca@linux.ibm.com> (raw)
Enable CONTEXT_ANALYSYS for s390/char drivers.
Static code checking for acquiring and releasing locks used to be done
with sparse. That was removed with [1] and replaced with a clang based
approach [2]. The new approach requires that each subsystem needs to be
explicitly enabled for checking.
Do that for drivers/s390/char. Add a __must_hold() attribute to
raw3215_make_room() to address the only valid warning.
Then enable CONTEXT_ANALYSIS.
Thanks,
Heiko
[1] 5b63d0ae94cc ("compiler-context-analysis: Remove Sparse support")
[2] 3269701cb256 ("compiler-context-analysis: Add infrastructure for Context Analysis with Clang")
Heiko Carstens (2):
s390/con3215: Add __must_hold() attribute to raw3215_make_room()
s390/char: Enable CONTEXT_ANALYSIS
drivers/s390/char/Makefile | 2 ++
drivers/s390/char/con3215.c | 1 +
2 files changed, 3 insertions(+)
--
2.53.0
next reply other threads:[~2026-08-06 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 15:53 Heiko Carstens [this message]
2026-08-06 15:53 ` [PATCH 1/2] s390/con3215: Add __must_hold() attribute to raw3215_make_room() Heiko Carstens
2026-08-06 16:12 ` sashiko-bot
2026-08-07 9:23 ` Sven Schnelle
2026-08-06 15:53 ` [PATCH 2/2] s390/char: Enable CONTEXT_ANALYSIS Heiko Carstens
2026-08-06 16:06 ` sashiko-bot
2026-08-07 9:23 ` Sven Schnelle
2026-08-07 10:49 ` [PATCH 0/2] " Heiko Carstens
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=20260806155303.2675932-1-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--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