From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw52056[1/1] net/mlx5: fix typos in comments
Date: 02 Apr 2019 01:15:01 -0700 [thread overview]
Message-ID: <e75792$6hi6hl@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3261 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/52056
_apply issues_
Submitter: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Date: 2019-04-02 07:40:05
Reply_mail: 1554190805-376-1-git-send-email-viacheslavo@mellanox.com
DPDK git baseline:
Repo:dpdk-master, CommitID: a9d64ecc4cc3ce1a48f96b06f24430900c15e728
Repo:dpdk-next-eventdev, CommitID: 7a1ccc24874e251957513aba0520500f873e276a
Repo:dpdk-next-net, CommitID: 484217a17ee094df024bfa19557c0a15537e7a57
Repo:dpdk-next-crypto, CommitID: b9bc82a71ea1faae88e535511213754004099b98
Repo:dpdk-next-virtio, CommitID: daf8de5c41dfbe40f354ff009f5791db348e0b09
*Repo: dpdk-master
Checking patch drivers/net/mlx5/mlx5.c...
error: while searching for:
/**
* Initialize DV/DR related data within private structure.
* Routine checks the reference counter and does actual
* resources creation/iniialization only if counter is zero.
*
* @param[in] priv
* Pointer to the private device data structure.
error: patch failed: drivers/net/mlx5/mlx5.c:300
error: drivers/net/mlx5/mlx5.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_tcf.c...
*Repo: dpdk-next-eventdev
Checking patch drivers/net/mlx5/mlx5.c...
error: while searching for:
/**
* Initialize DV/DR related data within private structure.
* Routine checks the reference counter and does actual
* resources creation/iniialization only if counter is zero.
*
* @param[in] priv
* Pointer to the private device data structure.
error: patch failed: drivers/net/mlx5/mlx5.c:300
error: drivers/net/mlx5/mlx5.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_tcf.c...
*Repo: dpdk-next-net
Checking patch drivers/net/mlx5/mlx5.c...
error: while searching for:
/**
* Initialize DV/DR related data within private structure.
* Routine checks the reference counter and does actual
* resources creation/iniialization only if counter is zero.
*
* @param[in] priv
* Pointer to the private device data structure.
error: patch failed: drivers/net/mlx5/mlx5.c:300
error: drivers/net/mlx5/mlx5.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_tcf.c...
*Repo: dpdk-next-crypto
Checking patch drivers/net/mlx5/mlx5.c...
error: while searching for:
/**
* Initialize DV/DR related data within private structure.
* Routine checks the reference counter and does actual
* resources creation/iniialization only if counter is zero.
*
* @param[in] priv
* Pointer to the private device data structure.
error: patch failed: drivers/net/mlx5/mlx5.c:300
error: drivers/net/mlx5/mlx5.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_tcf.c...
*Repo: dpdk-next-virtio
Checking patch drivers/net/mlx5/mlx5.c...
error: while searching for:
* port dedicated IB device, the context will be used by only given
* port due to unification.
*
* Routine first searches the context for the spesified IB device name,
* if found the shared context assumed and reference counter is incremented.
* If no context found the new one is created and initialized with specified
* IB device context and parameters.
error: patch failed: drivers/net/mlx5/mlx5.c:149
error: drivers/net/mlx5/mlx5.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_tcf.c...
DPDK STV team
reply other threads:[~2019-04-02 8:15 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='e75792$6hi6hl@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--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).