From: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
To: peterz@infradead.org
Cc: mingo@redhat.com, will@kernel.org, longman@redhat.com,
boqun.feng@gmail.com, linux-kernel@vger.kernel.org,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Subject: [PATCH] lockdep/selftests: Fix duplicate included locking-selftest-softirq.h
Date: Fri, 30 Jul 2021 18:24:42 +0800 [thread overview]
Message-ID: <1627640682-14225-1-git-send-email-jiapeng.chong@linux.alibaba.com> (raw)
Clean up the following includecheck warning:
./lib/locking-selftest.c: locking-selftest-softirq.h is included more
than once.
Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Fixes: cae2ed9aa573 ("[PATCH] lockdep: locking API self tests")
Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
---
lib/locking-selftest.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/lib/locking-selftest.c b/lib/locking-selftest.c
index 161108e..6010445 100644
--- a/lib/locking-selftest.c
+++ b/lib/locking-selftest.c
@@ -1252,7 +1252,6 @@ static void rwsem_ABBA3(void)
#include "locking-selftest-wlock.h"
GENERATE_PERMUTATIONS_3_EVENTS(irq_read_recursion2_hard_wlock)
-#include "locking-selftest-softirq.h"
#include "locking-selftest-rlock.h"
GENERATE_PERMUTATIONS_3_EVENTS(irq_read_recursion2_soft_rlock)
@@ -1306,7 +1305,6 @@ static void rwsem_ABBA3(void)
#include "locking-selftest-wlock.h"
GENERATE_PERMUTATIONS_3_EVENTS(irq_read_recursion3_hard_wlock)
-#include "locking-selftest-softirq.h"
#include "locking-selftest-rlock.h"
GENERATE_PERMUTATIONS_3_EVENTS(irq_read_recursion3_soft_rlock)
--
1.8.3.1
next reply other threads:[~2021-07-30 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 10:24 Jiapeng Chong [this message]
2021-07-30 10:36 ` [PATCH] lockdep/selftests: Fix duplicate included locking-selftest-softirq.h Boqun Feng
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=1627640682-14225-1-git-send-email-jiapeng.chong@linux.alibaba.com \
--to=jiapeng.chong@linux.alibaba.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@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).