From: Ben Dooks <ben.dooks@sifive.com>
To: u-boot@lists.denx.de
Cc: Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
Ben Dooks <ben.dooks@sifive.com>
Subject: [PATCH 3/3] riscv: define test_and_{set,clear}_bit in asm/bitops.h
Date: Fri, 5 May 2023 09:02:07 +0100 [thread overview]
Message-ID: <20230505080207.11902-4-ben.dooks@sifive.com> (raw)
In-Reply-To: <20230505080207.11902-1-ben.dooks@sifive.com>
These seem to be missing, and trying to build ubifs without them
is causing errors due to these being missing.
Signed-off-by: Ben Dooks <ben.dooks@sifive.com>
---
arch/riscv/include/asm/bitops.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/riscv/include/asm/bitops.h b/arch/riscv/include/asm/bitops.h
index 536629bbec..35f1368b83 100644
--- a/arch/riscv/include/asm/bitops.h
+++ b/arch/riscv/include/asm/bitops.h
@@ -158,6 +158,9 @@ static inline unsigned long ffz(unsigned long word)
#define hweight16(x) generic_hweight16(x)
#define hweight8(x) generic_hweight8(x)
+#define test_and_set_bit __test_and_set_bit
+#define test_and_clear_bit __test_and_clear_bit
+
#define ext2_set_bit test_and_set_bit
#define ext2_clear_bit test_and_clear_bit
#define ext2_test_bit test_bit
--
2.39.2
next prev parent reply other threads:[~2023-05-05 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 8:02 riscv: asm update for building ubifs Ben Dooks
2023-05-05 8:02 ` [PATCH 1/3] riscv: add generic link for <asm/atomic.h> Ben Dooks
2023-06-12 7:31 ` Leo Liang
2023-05-05 8:02 ` [PATCH 2/3] riscv: implement local_irq_{save,restore} macros Ben Dooks
2023-06-12 7:47 ` Leo Liang
2023-06-23 9:57 ` Ben Dooks
2023-05-05 8:02 ` Ben Dooks [this message]
2023-06-12 7:48 ` [PATCH 3/3] riscv: define test_and_{set,clear}_bit in asm/bitops.h Leo Liang
2023-05-11 11:56 ` riscv: asm update for building ubifs Conor Dooley
2023-05-25 11:01 ` Ben Dooks
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=20230505080207.11902-4-ben.dooks@sifive.com \
--to=ben.dooks@sifive.com \
--cc=rick@andestech.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.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