From: Heiko Carstens <hca@linux.ibm.com>
To: "Jens Axboe" <axboe@kernel.dk>,
"Stefan Haberland" <sth@linux.ibm.com>,
"Jan Höppner" <hoeppner@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-block@vger.kernel.org
Subject: [PATCH 2/2] s390/block: Enable CONTEXT_ANALYSIS
Date: Thu, 6 Aug 2026 15:00:50 +0200 [thread overview]
Message-ID: <20260806130050.2057443-3-hca@linux.ibm.com> (raw)
In-Reply-To: <20260806130050.2057443-1-hca@linux.ibm.com>
All drivers in drivers/s390/block pass clang's compile time context
analysis. Therefore enable CONTEXT_ANALYSIS.
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
---
drivers/s390/block/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/s390/block/Makefile b/drivers/s390/block/Makefile
index a0a54d2f063f..3dd1a3ce7ed1 100644
--- a/drivers/s390/block/Makefile
+++ b/drivers/s390/block/Makefile
@@ -3,6 +3,8 @@
# S/390 block devices
#
+CONTEXT_ANALYSIS := y
+
dasd_eckd_mod-objs := dasd_eckd.o dasd_3990_erp.o dasd_alias.o
dasd_fba_mod-objs := dasd_fba.o
dasd_diag_mod-objs := dasd_diag.o
--
2.53.0
next prev parent reply other threads:[~2026-08-06 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 13:00 [PATCH 0/2] s390/block: Enable CONTEXT_ANALYSIS Heiko Carstens
2026-08-06 13:00 ` [PATCH 1/2] s390/dasd: Add __context_unsafe() attribute to various functions Heiko Carstens
2026-08-06 13:09 ` sashiko-bot
2026-08-06 14:06 ` Heiko Carstens
2026-08-06 14:09 ` Stefan Haberland
2026-08-06 16:34 ` Bart Van Assche
2026-08-06 18:09 ` Heiko Carstens
2026-08-06 13:00 ` Heiko Carstens [this message]
2026-08-06 13:02 ` [PATCH 2/2] s390/block: Enable CONTEXT_ANALYSIS sashiko-bot
2026-08-06 16:34 ` Bart Van Assche
2026-08-06 13:09 ` [PATCH 0/2] " Stefan Haberland
2026-08-06 14:14 ` Jens Axboe
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=20260806130050.2057443-3-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=hoeppner@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sth@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 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.