From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>, zhoumin@loongson.cn
Subject: |WARNING| pw134471 The problem with priv_data in crypto and security API's
Date: Mon, 20 Nov 2023 03:40:48 +0800 [thread overview]
Message-ID: <202311191940.3AJJem73587986@localhost.localdomain> (raw)
In-Reply-To: <20231119115809.6303bd89@hermes.local>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/134471
_apply patch failure_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Sun, 19 Nov 2023 11:58:09 -0800
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 23a458e2ee9c760dbc279eda877170f4a4555aa9
Apply patch set 134471 failed:
error: corrupt patch at line 211
parent reply other threads:[~2023-11-19 20:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20231119115809.6303bd89@hermes.local>]
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=202311191940.3AJJem73587986@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).