automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |WARNING| pw(94287) sid(17349) [v1, 14/14] common/mlx5: clean up legacy PCI bus driver
Date: 15 Jun 2021 21:16:28 -0700	[thread overview]
Message-ID: <f381f8$ee8nuf@orsmga001-auth.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]


Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/94287

_apply issues_

Submitter: Xueming Li <xuemingl@nvidia.com>
Date: 2021-06-16 04:09:35
Reply_mail: 20210616040935.311733-15-xuemingl@nvidia.com

DPDK git baseline:
	Repo:dpdk, CommitID: 2ca92f54410400af76a1f0bc3bfecc8077e282aa


* Repo: dpdk
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-shz.intel.com
Starting new HTTP connection (1): proxy-shz.intel.com
error: patch failed: drivers/net/mlx5/mlx5_mr.c:394
error: drivers/net/mlx5/mlx5_mr.c: patch does not apply
Applying: common/mlx5: add common device driver
Applying: common/mlx5: move description of PCI sysfs functions
--
Applying: common/mlx5: get PCI device address from any bus
Applying: net/mlx5: remove PCI dependency
Applying: net/mlx5: migrate to bus-agnostic common driver
Patch failed at 0006 net/mlx5: migrate to bus-agnostic common driver
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team

                 reply	other threads:[~2021-06-16  4:16 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='f381f8$ee8nuf@orsmga001-auth.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).