From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw108601-108605 [PATCH] [5/5] doc/linux_gsg: expand list of directories
Date: Tue, 8 Mar 2022 10:08:27 -0500 (EST) [thread overview]
Message-ID: <20220308150827.E12E2B27D@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/108601
_apply patch failure_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, March 08 2022 14:50:01
Applied on: CommitID:2479a1e9a8886c93ba4c8a7aa2a35a04302f1aae
Apply patch set 108601-108605 failed:
Checking patch doc/guides/linux_gsg/sys_reqs.rst...
error: while searching for:
This chapter describes the packages required to compile the DPDK.
.. note::
If the DPDK is being used on an Intel\ |reg| Communications Chipset 89xx Series platform,
please consult the *Intel\ |reg| Communications Chipset 89xx Series Software for Linux Getting Started Guide*.
BIOS Setting Prerequisite on x86
--------------------------------
error: patch failed: doc/guides/linux_gsg/sys_reqs.rst:8
Applying patch doc/guides/linux_gsg/sys_reqs.rst with 1 reject...
Rejected hunk #1.
diff a/doc/guides/linux_gsg/sys_reqs.rst b/doc/guides/linux_gsg/sys_reqs.rst (rejected hunks)
@@ -8,11 +8,6 @@ System Requirements
This chapter describes the packages required to compile the DPDK.
-.. note::
-
- If the DPDK is being used on an Intel\ |reg| Communications Chipset 89xx Series platform,
- please consult the *Intel\ |reg| Communications Chipset 89xx Series Software for Linux Getting Started Guide*.
-
BIOS Setting Prerequisite on x86
--------------------------------
https://lab.dpdk.org/results/dashboard/patchsets/21436/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-03-08 15:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220308150827.E12E2B27D@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
/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).