From: Andrea Parri <andrea.parri@amarulasolutions.com>
To: linux-kernel@vger.kernel.org
Cc: Andrea Parri <andrea.parri@amarulasolutions.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
uclinux-h8-devel@lists.sourceforge.jp
Subject: [PATCH 2/2] h8300/bitops: Remove smp_mb__{before,after}_clear_bit()
Date: Tue, 25 Sep 2018 14:12:25 +0200 [thread overview]
Message-ID: <20180925121225.9917-3-andrea.parri@amarulasolutions.com> (raw)
In-Reply-To: <20180925121225.9917-1-andrea.parri@amarulasolutions.com>
The barriers are unused; remove their definition.
Signed-off-by: Andrea Parri <andrea.parri@amarulasolutions.com>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: <uclinux-h8-devel@lists.sourceforge.jp>
---
arch/h8300/include/asm/bitops.h | 6 ------
1 file changed, 6 deletions(-)
diff --git a/arch/h8300/include/asm/bitops.h b/arch/h8300/include/asm/bitops.h
index 647a83bd40b70..7aa16c732aa9f 100644
--- a/arch/h8300/include/asm/bitops.h
+++ b/arch/h8300/include/asm/bitops.h
@@ -51,12 +51,6 @@ static inline void FNAME(int nr, volatile unsigned long *addr) \
} \
}
-/*
- * clear_bit() doesn't provide any barrier for the compiler.
- */
-#define smp_mb__before_clear_bit() barrier()
-#define smp_mb__after_clear_bit() barrier()
-
H8300_GEN_BITOP(set_bit, "bset")
H8300_GEN_BITOP(clear_bit, "bclr")
H8300_GEN_BITOP(change_bit, "bnot")
--
2.17.1
prev parent reply other threads:[~2018-09-25 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 12:12 [PATCH trivial 0/2] h8300, riscv: Remove smp_mb__{before,after}_clear_bit() Andrea Parri
2018-09-25 12:12 ` [PATCH 1/2] riscv/bitops: " Andrea Parri
2018-09-25 17:19 ` Palmer Dabbelt
2018-09-25 17:49 ` Andrea Parri
2018-09-25 17:57 ` Palmer Dabbelt
2018-09-25 12:12 ` Andrea Parri [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=20180925121225.9917-3-andrea.parri@amarulasolutions.com \
--to=andrea.parri@amarulasolutions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.sourceforge.jp \
/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).