From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |WARNING| pw103381-103383 [PATCH] [v3, 3/3] doc: add protocol agnostic flow offloading for RSS
Date: Wed, 3 Nov 2021 15:54:05 +0000 (UTC) [thread overview]
Message-ID: <20211103155405.9CB3B60796@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/103381
_apply patch failure_
Submitter: Ting Xu <ting.xu@intel.com>
Date: Tuesday, November 02 2021 01:49:43
Applied on: CommitID:b2be63b55ab086c52c082d5c0b2b01fffbc48326
Apply patch set 103381-103383 failed:
Checking patch drivers/common/qat/dev/qat_dev_gen1.c...
error: drivers/common/qat/dev/qat_dev_gen1.c: does not exist in index
https://lab.dpdk.org/results/dashboard/patchsets/19896/
UNH-IOL DPDK Community Lab
next reply other threads:[~2021-11-03 15:54 UTC|newest]
Thread overview: 174+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 15:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-03 16:00 dpdklab
2021-11-03 15:59 dpdklab
2021-11-03 15:59 dpdklab
2021-11-03 15:59 dpdklab
2021-11-03 15:58 dpdklab
2021-11-03 15:58 dpdklab
2021-11-03 15:57 dpdklab
2021-11-03 15:57 dpdklab
2021-11-03 15:57 dpdklab
2021-11-03 15:56 dpdklab
2021-11-03 15:56 dpdklab
2021-11-03 15:56 dpdklab
2021-11-03 15:55 dpdklab
2021-11-03 15:55 dpdklab
2021-11-03 15:55 dpdklab
2021-11-03 15:54 dpdklab
2021-11-03 15:54 dpdklab
2021-11-03 15:54 dpdklab
2021-11-03 15:53 dpdklab
2021-11-03 15:53 dpdklab
2021-11-03 15:53 dpdklab
2021-11-03 15:53 dpdklab
2021-11-03 15:52 dpdklab
2021-11-03 15:52 dpdklab
2021-11-03 15:52 dpdklab
2021-11-03 15:51 dpdklab
2021-11-03 15:51 dpdklab
2021-11-03 15:51 dpdklab
2021-11-03 15:51 dpdklab
2021-11-03 15:50 dpdklab
2021-11-03 15:50 dpdklab
2021-11-03 15:50 dpdklab
2021-11-03 15:49 dpdklab
2021-11-03 15:49 dpdklab
2021-11-03 15:49 dpdklab
2021-11-03 15:49 dpdklab
2021-11-03 15:48 dpdklab
2021-11-03 15:48 dpdklab
2021-11-03 15:48 dpdklab
2021-11-03 15:48 dpdklab
2021-11-03 15:47 dpdklab
2021-11-03 15:47 dpdklab
2021-11-03 15:47 dpdklab
2021-11-03 15:46 dpdklab
2021-11-03 15:46 dpdklab
2021-11-03 15:46 dpdklab
2021-11-03 15:46 dpdklab
2021-11-03 15:45 dpdklab
2021-11-03 15:45 dpdklab
2021-11-03 15:45 dpdklab
2021-11-03 15:44 dpdklab
2021-11-03 15:44 dpdklab
2021-11-03 15:44 dpdklab
2021-11-03 15:44 dpdklab
2021-11-03 15:43 dpdklab
2021-11-03 15:43 dpdklab
2021-11-03 15:43 dpdklab
2021-11-03 15:42 dpdklab
2021-11-03 15:42 dpdklab
2021-11-03 15:42 dpdklab
2021-11-03 15:42 dpdklab
2021-11-03 15:41 dpdklab
2021-11-03 15:41 dpdklab
2021-11-03 15:41 dpdklab
2021-11-03 15:40 dpdklab
2021-11-03 15:40 dpdklab
2021-11-03 15:40 dpdklab
2021-11-03 15:39 dpdklab
2021-11-03 15:39 dpdklab
2021-11-03 15:39 dpdklab
2021-11-03 15:38 dpdklab
2021-11-03 15:38 dpdklab
2021-11-03 15:38 dpdklab
2021-11-03 15:37 dpdklab
2021-11-03 15:37 dpdklab
2021-11-03 15:37 dpdklab
2021-11-03 15:36 dpdklab
2021-11-03 15:36 dpdklab
2021-11-03 15:36 dpdklab
2021-11-03 15:35 dpdklab
2021-11-03 15:35 dpdklab
2021-11-03 15:35 dpdklab
2021-11-03 15:35 dpdklab
2021-11-03 15:34 dpdklab
2021-11-03 15:34 dpdklab
2021-11-03 15:34 dpdklab
2021-11-03 15:33 dpdklab
2021-11-03 15:33 dpdklab
2021-11-03 15:33 dpdklab
2021-11-03 15:33 dpdklab
2021-11-03 15:32 dpdklab
2021-11-03 15:32 dpdklab
2021-11-03 15:32 dpdklab
2021-11-03 15:31 dpdklab
2021-11-03 15:31 dpdklab
2021-11-03 15:31 dpdklab
2021-11-03 15:31 dpdklab
2021-11-03 15:30 dpdklab
2021-11-03 15:30 dpdklab
2021-11-03 15:30 dpdklab
2021-11-03 15:29 dpdklab
2021-11-03 15:29 dpdklab
2021-11-03 15:29 dpdklab
2021-11-03 15:29 dpdklab
2021-11-03 15:28 dpdklab
2021-11-03 15:28 dpdklab
2021-11-03 15:28 dpdklab
2021-11-03 15:27 dpdklab
2021-11-03 15:27 dpdklab
2021-11-03 15:27 dpdklab
2021-11-03 15:27 dpdklab
2021-11-03 15:26 dpdklab
2021-11-03 15:26 dpdklab
2021-11-03 15:25 dpdklab
2021-11-03 15:25 dpdklab
2021-11-03 15:25 dpdklab
2021-11-03 15:25 dpdklab
2021-11-03 15:24 dpdklab
2021-11-03 15:24 dpdklab
2021-11-03 15:24 dpdklab
2021-11-03 15:24 dpdklab
2021-11-03 15:24 dpdklab
2021-11-03 15:23 dpdklab
2021-11-03 15:23 dpdklab
2021-11-03 15:23 dpdklab
2021-11-03 15:23 dpdklab
2021-11-03 15:22 dpdklab
2021-11-03 15:22 dpdklab
2021-11-03 15:22 dpdklab
2021-11-03 15:21 dpdklab
2021-11-03 15:21 dpdklab
2021-11-03 15:21 dpdklab
2021-11-03 15:20 dpdklab
2021-11-03 15:20 dpdklab
2021-11-03 15:19 dpdklab
2021-11-03 15:19 dpdklab
2021-11-03 15:19 dpdklab
2021-11-03 15:18 dpdklab
2021-11-03 15:18 dpdklab
2021-11-03 15:18 dpdklab
2021-11-03 15:17 dpdklab
2021-11-03 15:17 dpdklab
2021-11-03 15:17 dpdklab
2021-11-03 15:17 dpdklab
2021-11-03 15:16 dpdklab
2021-11-03 15:16 dpdklab
2021-11-03 15:16 dpdklab
2021-11-03 15:15 dpdklab
2021-11-03 15:15 dpdklab
2021-11-03 15:15 dpdklab
2021-11-03 15:14 dpdklab
2021-11-03 15:14 dpdklab
2021-11-03 15:14 dpdklab
2021-11-03 15:14 dpdklab
2021-11-03 15:13 dpdklab
2021-11-03 15:13 dpdklab
2021-11-03 15:13 dpdklab
2021-11-03 15:12 dpdklab
2021-11-03 15:12 dpdklab
2021-11-03 15:12 dpdklab
2021-11-03 15:11 dpdklab
2021-11-03 15:11 dpdklab
2021-11-03 15:11 dpdklab
2021-11-03 15:10 dpdklab
2021-11-03 15:10 dpdklab
2021-11-03 15:10 dpdklab
2021-11-03 15:09 dpdklab
2021-11-03 15:09 dpdklab
2021-11-03 15:09 dpdklab
2021-11-03 15:08 dpdklab
2021-11-03 15:08 dpdklab
2021-11-03 15:08 dpdklab
2021-11-03 15:07 dpdklab
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=20211103155405.9CB3B60796@dpdk-ubuntu.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).