From: zhoumin <zhoumin@loongson.cn>
To: David Marchand <david.marchand@redhat.com>
Cc: thomas@monjalon.net, bruce.richardson@intel.com,
anatoly.burakov@intel.com, qiming.yang@intel.com,
Yuying.Zhang@intel.com, jgrajcia@cisco.com,
konstantin.v.ananyev@yandex.ru, dev@dpdk.org,
maobibo@loongson.cn
Subject: Re: [PATCH v7 0/7] Introduce support for LoongArch architecture
Date: Tue, 4 Oct 2022 16:50:05 +0800 [thread overview]
Message-ID: <cb626ab5-8740-1ce7-4171-25ca887906a5@loongson.cn> (raw)
In-Reply-To: <CAJFAV8xeOXXrxMy4FzHTCO6WoOoTGjtEswOdAeOPDNq5tznMUA@mail.gmail.com>
On Tue, Oct 4, 2022 at 14:59, David Marchand wrote:
> On Fri, Sep 30, 2022 at 10:02 AM Min Zhou <zhoumin@loongson.cn> wrote:
>> Dear team,
>>
>> The following patch set is intended to support DPDK running on LoongArch
>> architecture.
>>
>> LoongArch is the general processor architecture of Loongson Corporation
>> and is a new RISC ISA, which is a bit like MIPS or RISC-V.
>>
>> The online documents of LoongArch architecture are here:
>> https://loongson.github.io/LoongArch-Documentation/README-EN.html
>>
>> The latest build tools for LoongArch (binary) can be downloaded from:
>> https://github.com/loongson/build-tools
>>
>> v7:
>> - rebase the patchset on the main repository
>> - add errno.h to rte_power_intrinsics.c according with
>> commit 72b452c5f259
> I did some comments on patch 1.
Yes, thanks. I have read them carefully and prepare to send the v8 patchset.
> I am still considering the patch 7 (hooking into GHA) but the rest
> looks good enough to me.
Yes, thanks. The changes in the patch 7 is indeed not good for adding CI
for LoongArch.
As we discussed last weekend, it is better to set up a CI system for
LoongArch and integrate
the test results of new patch to Patchwork. We are building the CI
system, but it will take
some time.
> Could you respin the series?
OK, thank. I will send the v8 patchset to fix them.
>
> Thanks!
Thanks,
--
Min Zhou
prev parent reply other threads:[~2022-10-04 8:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 8:02 Min Zhou
2022-09-30 8:02 ` [PATCH v7 1/7] eal/loongarch: support " Min Zhou
2022-10-03 17:15 ` David Marchand
2022-10-04 8:49 ` zhoumin
2022-09-30 8:02 ` [PATCH v7 2/7] net/ixgbe: add vector stubs for LoongArch Min Zhou
2022-09-30 8:02 ` [PATCH v7 3/7] net/memif: set memfd syscall ID on LoongArch Min Zhou
2022-09-30 8:02 ` [PATCH v7 4/7] net/tap: set BPF syscall ID for LoongArch Min Zhou
2022-09-30 8:02 ` [PATCH v7 5/7] examples/l3fwd: enable LoongArch operation Min Zhou
2022-09-30 8:02 ` [PATCH v7 6/7] test/cpuflags: add test for LoongArch cpu flag Min Zhou
2022-09-30 8:02 ` [PATCH v7 7/7] ci: add LOONGARCH64 cross compilation job Min Zhou
2022-09-30 8:13 ` [PATCH v7 0/7] Introduce support for LoongArch architecture David Marchand
2022-09-30 10:05 ` zhoumin
2022-09-30 14:20 ` David Marchand
2022-10-01 14:25 ` zhoumin
2022-10-03 16:30 ` David Marchand
2022-10-04 8:49 ` zhoumin
2022-10-03 8:14 ` Ali Alnubani
2022-10-03 12:44 ` zhoumin
2022-10-04 6:59 ` David Marchand
2022-10-04 8:50 ` zhoumin [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=cb626ab5-8740-1ce7-4171-25ca887906a5@loongson.cn \
--to=zhoumin@loongson.cn \
--cc=Yuying.Zhang@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=maobibo@loongson.cn \
--cc=qiming.yang@intel.com \
--cc=thomas@monjalon.net \
/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).