From: zhoumin <zhoumin@loongson.cn>
To: David Marchand <david.marchand@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Bruce Richardson <bruce.richardson@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
Qiming Yang <qiming.yang@intel.com>,
Yuying Zhang <Yuying.Zhang@intel.com>,
Jakub Grajciar <jgrajcia@cisco.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
dev <dev@dpdk.org>,
maobibo@loongson.cn, zhoumin@loongson.cn
Subject: Re: [PATCH v5 1/7] eal/loongarch: support LoongArch architecture
Date: Fri, 26 Aug 2022 16:48:09 +0800 [thread overview]
Message-ID: <ec45eb89-f9fb-a609-1d22-6e71066c31c0@loongson.cn> (raw)
In-Reply-To: <CAJFAV8xtLEGCPrDRUJUpmuuUVMFiyYbsRHHcyTjeVEsDYi+LYw@mail.gmail.com>
Hi David,
Thank you very much for your reminder.
On Thu, Aug 25, 2022 at 22:04, David Marchand wrote:
> On Thu, Aug 25, 2022 at 3:56 PM David Marchand
> <david.marchand@redhat.com> wrote:
>> This is only a first pass.
> Additionnally, please run ./devtools/check-meson.py.
> I see tabulations where we expect spaces.
OK, thanks. I just became aware of these errors that this
tool has reported. I will fix them.
--
Thanks,
Min Zhou
next prev parent reply other threads:[~2022-08-26 8:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 8:31 [PATCH v5 0/7] Introduce support for " Min Zhou
2022-08-24 8:31 ` [PATCH v5 1/7] eal/loongarch: support " Min Zhou
2022-08-25 13:56 ` David Marchand
2022-08-25 14:04 ` David Marchand
2022-08-26 8:48 ` zhoumin [this message]
2022-08-26 8:34 ` zhoumin
2022-08-24 8:31 ` [PATCH v5 2/7] net/ixgbe: add vector stubs for LoongArch Min Zhou
2022-08-24 8:31 ` [PATCH v5 3/7] net/memif: set memfd syscall ID on LoongArch Min Zhou
2022-08-24 8:31 ` [PATCH v5 4/7] net/tap: set BPF syscall ID for LoongArch Min Zhou
2022-08-24 8:31 ` [PATCH v5 5/7] examples/l3fwd: enable LoongArch operation Min Zhou
2022-08-24 8:31 ` [PATCH v5 6/7] test/cpuflags: add test for LoongArch cpu flag Min Zhou
2022-08-24 8:31 ` [PATCH v5 7/7] ci: add LOONGARCH64 cross compilation job Min Zhou
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=ec45eb89-f9fb-a609-1d22-6e71066c31c0@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).