From: Thomas Monjalon <thomas@monjalon.net>
To: Sun Yuechi <sunyuechi@iscas.ac.cn>
Cc: dev@dpdk.org, "Stanisław Kardach" <stanislaw.kardach@gmail.com>,
"Bruce Richardson" <bruce.richardson@intel.com>,
"Qiguo Chen" <chen.qiguo@zte.com.cn>,
"Daniel Gregory" <daniel.gregory@bytedance.com>,
"Liang Ma" <liangma@liangbit.com>,
"Punit Agrawal" <punit.agrawal@bytedance.com>,
"Pengcheng Wang" <wangpengcheng.pp@bytedance.com>,
"Chunsong Feng" <fengchunsong@bytedance.com>
Subject: Re: [PATCH] config/riscv: add rv64gcv cross compilation target
Date: Sun, 09 Nov 2025 22:38:43 +0100 [thread overview]
Message-ID: <2429522.4MS8fQxZnU@thomas> (raw)
In-Reply-To: <20250923150734.2208125-1-sunyuechi@iscas.ac.cn>
23/09/2025 17:07, sunyuechi@iscas.ac.cn:
> From: Sun Yuechi <sunyuechi@iscas.ac.cn>
>
> Add a cross file for rv64gcv, enable it in devtools/test-meson-builds.sh,
> and update the RISC-V cross-build guide to support the vector extension.
>
> Signed-off-by: Sun Yuechi <sunyuechi@iscas.ac.cn>
In general for RISC-V patches, I wish to see more collaboration
between contributors interested by this architecture.
This patch has no review but looks harmless,
except adding one more build in devtools/test-meson-builds.sh.
I'm not sure we want to run this build in most CI runs.
Maybe we want to replace the generic RISC-V build with the vector one.
It could be discussed in another patch.
Applied without adding in test-meson-builds.sh, thanks.
prev parent reply other threads:[~2025-11-09 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 15:07 sunyuechi
2025-10-06 12:43 ` sunyuechi
2025-10-27 1:53 ` sunyuechi
2025-11-07 13:36 ` sunyuechi
2025-11-09 21:38 ` Thomas Monjalon [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=2429522.4MS8fQxZnU@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=chen.qiguo@zte.com.cn \
--cc=daniel.gregory@bytedance.com \
--cc=dev@dpdk.org \
--cc=fengchunsong@bytedance.com \
--cc=liangma@liangbit.com \
--cc=punit.agrawal@bytedance.com \
--cc=stanislaw.kardach@gmail.com \
--cc=sunyuechi@iscas.ac.cn \
--cc=wangpengcheng.pp@bytedance.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;
as well as URLs for NNTP newsgroup(s).