From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: David Young <dave@youngcopy.com>, zhoumin@loongson.cn
Subject: |WARNING| pw133689-133691 [PATCH 1/3] GSG Section 1: Introduction - Updated based on feedback
Date: Wed, 1 Nov 2023 08:30:15 +0800 [thread overview]
Message-ID: <202311010030.3A10UFmM371218@localhost.localdomain> (raw)
In-Reply-To: <20231101004932.1371-2-dave@youngcopy.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/133689
_apply patch failure_
Submitter: David Young <dave@youngcopy.com>
Date: Tue, 31 Oct 2023 20:49:26 -0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 1025bd1c24b1be70e028c7ba0595782bce75fcc6
Apply patch set 133689-133691 failed:
Checking patch doc/guides/getting_started_guide/intro.rst...
error: doc/guides/getting_started_guide/intro.rst: No such file or directory
next parent reply other threads:[~2023-11-01 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231101004932.1371-2-dave@youngcopy.com>
2023-11-01 0:30 ` qemudev [this message]
2023-11-01 0:52 ` |WARNING| pw133689 " checkpatch
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=202311010030.3A10UFmM371218@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=dave@youngcopy.com \
--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).