From: Marco Elver <elver@google.com>
To: elver@google.com
Cc: paulmck@kernel.org, andreyknvl@google.com, glider@google.com,
dvyukov@google.com, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/5] compiler.h, seqlock.h: Remove unnecessary kcsan.h includes
Date: Mon, 10 Feb 2020 19:43:14 +0100 [thread overview]
Message-ID: <20200210184317.233039-2-elver@google.com> (raw)
In-Reply-To: <20200210184317.233039-1-elver@google.com>
No we longer have to include kcsan.h, since the required KCSAN interface
for both compiler.h and seqlock.h are now provided by kcsan-checks.h.
Signed-off-by: Marco Elver <elver@google.com>
---
include/linux/compiler.h | 2 --
include/linux/seqlock.h | 2 +-
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/include/linux/compiler.h b/include/linux/compiler.h
index c1bdf37571cb8..f504edebd5d71 100644
--- a/include/linux/compiler.h
+++ b/include/linux/compiler.h
@@ -313,8 +313,6 @@ unsigned long read_word_at_a_time(const void *addr)
__u.__val; \
})
-#include <linux/kcsan.h>
-
/**
* data_race - mark an expression as containing intentional data races
*
diff --git a/include/linux/seqlock.h b/include/linux/seqlock.h
index 239701cae3764..8b97204f35a77 100644
--- a/include/linux/seqlock.h
+++ b/include/linux/seqlock.h
@@ -37,7 +37,7 @@
#include <linux/preempt.h>
#include <linux/lockdep.h>
#include <linux/compiler.h>
-#include <linux/kcsan.h>
+#include <linux/kcsan-checks.h>
#include <asm/processor.h>
/*
--
2.25.0.341.g760bfbb309-goog
next prev parent reply other threads:[~2020-02-10 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 18:43 [PATCH 1/5] kcsan: Move interfaces that affects checks to kcsan-checks.h Marco Elver
2020-02-10 18:43 ` Marco Elver [this message]
2020-02-10 18:43 ` [PATCH 3/5] kcsan: Introduce kcsan_value_change type Marco Elver
2020-02-10 18:43 ` [PATCH 4/5] kcsan: Add kcsan_set_access_mask() support Marco Elver
2020-02-10 18:43 ` [PATCH 5/5] kcsan: Introduce ASSERT_EXCLUSIVE_BITS(var, mask) Marco Elver
2020-02-10 21:07 ` John Hubbard
2020-02-11 16:07 ` Marco Elver
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=20200210184317.233039-2-elver@google.com \
--to=elver@google.com \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).