From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>, zhoumin@loongson.cn
Subject: |WARNING| pw75565-138663 [PATCH] eal: add option to put timestamp on console output
Date: Thu, 21 Mar 2024 23:47:59 +0800 [thread overview]
Message-ID: <202403211547.42LFlxdt928457@localhost.localdomain> (raw)
In-Reply-To: <20200814173441.23086-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/75565
_apply patch failure_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 14 Aug 2020 10:34:41 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
Apply patch set 75565-138663 failed:
Checking patch doc/guides/linux_gsg/linux_eal_parameters.rst...
Hunk #1 succeeded at 135 (offset 17 lines).
Checking patch lib/librte_eal/common/eal_common_options.c...
error: lib/librte_eal/common/eal_common_options.c: No such file or directory
Checking patch lib/librte_eal/common/eal_internal_cfg.h...
error: lib/librte_eal/common/eal_internal_cfg.h: No such file or directory
Checking patch lib/librte_eal/common/eal_options.h...
error: lib/librte_eal/common/eal_options.h: No such file or directory
Checking patch lib/librte_eal/linux/eal_log.c...
error: lib/librte_eal/linux/eal_log.c: No such file or directory
next prev parent reply other threads:[~2024-03-21 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200814173441.23086-1-stephen@networkplumber.org>
2020-08-14 17:35 ` [dpdk-test-report] |SUCCESS| pw75565 " checkpatch
2024-03-21 15:47 ` qemudev [this message]
2024-11-08 8:24 ` |WARNING| pw75565-148129 " qemudev
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=202403211547.42LFlxdt928457@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=stephen@networkplumber.org \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.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 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).