From: Nam Cao <namcao@linutronix.de>
To: "Vivian Wang" <wangruikang@iscas.ac.cn>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"André Almeida" <andrealmeid@igalia.com>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Thomas Gleixner" <tglx@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>
Subject: Re: [PATCH v3 4/5] riscv: compat_vdso: Build with zacas if available
Date: Mon, 20 Jul 2026 13:17:02 +0200 [thread overview]
Message-ID: <87o6g1ewr5.fsf@yellow.woof> (raw)
In-Reply-To: <0e65ddab-f066-4d9a-b032-d1e55e76fe47@iscas.ac.cn>
Vivian Wang <wangruikang@iscas.ac.cn> writes:
> I'm wondering if you would be interested in using .option arch, +zacas
> for this, instead of enabling it for everything.
Sure, I don't see any downside of that.
Nam
WARNING: multiple messages have this Message-ID (diff)
From: Nam Cao <namcao@linutronix.de>
To: "Vivian Wang" <wangruikang@iscas.ac.cn>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"André Almeida" <andrealmeid@igalia.com>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Thomas Gleixner" <tglx@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>
Subject: Re: [PATCH v3 4/5] riscv: compat_vdso: Build with zacas if available
Date: Mon, 20 Jul 2026 13:17:02 +0200 [thread overview]
Message-ID: <87o6g1ewr5.fsf@yellow.woof> (raw)
In-Reply-To: <0e65ddab-f066-4d9a-b032-d1e55e76fe47@iscas.ac.cn>
Vivian Wang <wangruikang@iscas.ac.cn> writes:
> I'm wondering if you would be interested in using .option arch, +zacas
> for this, instead of enabling it for everything.
Sure, I don't see any downside of that.
Nam
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-07-20 11:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 8:06 [PATCH v3 0/5] riscv: vdso: Implement __vdso_futex_robust_try_unlock() Nam Cao
2026-07-17 8:06 ` Nam Cao
2026-07-17 8:06 ` [PATCH v3 1/5] riscv: compat_vdso: switch to standard kbuild rule Nam Cao
2026-07-17 8:06 ` Nam Cao
2026-07-17 12:17 ` Thomas Weißschuh
2026-07-17 12:17 ` Thomas Weißschuh
2026-07-17 8:06 ` [PATCH v3 2/5] riscv: compat_vdso: Allow *.c source files Nam Cao
2026-07-17 8:06 ` Nam Cao
2026-07-17 12:19 ` Thomas Weißschuh
2026-07-17 12:19 ` Thomas Weißschuh
2026-07-17 8:06 ` [PATCH v3 3/5] riscv: compat_vdso: Introduce COMPAT_MARCH variable Nam Cao
2026-07-17 8:06 ` Nam Cao
2026-07-17 12:19 ` Thomas Weißschuh
2026-07-17 12:19 ` Thomas Weißschuh
2026-07-17 8:06 ` [PATCH v3 4/5] riscv: compat_vdso: Build with zacas if available Nam Cao
2026-07-17 8:06 ` Nam Cao
2026-07-17 12:23 ` Thomas Weißschuh
2026-07-17 12:23 ` Thomas Weißschuh
2026-07-17 12:38 ` Vivian Wang
2026-07-17 12:38 ` Vivian Wang
2026-07-17 12:44 ` Vivian Wang
2026-07-17 12:44 ` Vivian Wang
2026-07-20 11:17 ` Nam Cao [this message]
2026-07-20 11:17 ` Nam Cao
2026-07-17 8:06 ` [PATCH v3 5/5] riscv: vdso: Implement __vdso_futex_robust_try_unlock() Nam Cao
2026-07-17 8:06 ` Nam Cao
2026-07-17 12:37 ` Thomas Weißschuh
2026-07-17 12:37 ` Thomas Weißschuh
2026-07-20 11:37 ` Nam Cao
2026-07-20 11:37 ` Nam Cao
2026-07-20 11:42 ` Thomas Weißschuh
2026-07-20 11:42 ` Thomas Weißschuh
2026-07-20 11:50 ` Nam Cao
2026-07-20 11:50 ` Nam Cao
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=87o6g1ewr5.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=alex@ghiti.fr \
--cc=andrealmeid@igalia.com \
--cc=aou@eecs.berkeley.edu \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=tglx@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=wangruikang@iscas.ac.cn \
/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.