automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, 4plague@gmail.com
Subject: compilation|WARNING| pw(150287) sid(34400) job(PER_PATCH_BUILD14648)doc/guides: Mention needed kernel option for mlx5 multiport e-switch
Date: 20 Jan 2025 06:23:15 -0800	[thread overview]
Message-ID: <68906f$3aben5@ORVIESA003-auth.jf.intel.com> (raw)

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


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

_apply issues_

Submitter: Plague <4plague@gmail.com>
Date: 2025-01-20 14:14:37
Reply_mail: <CA++ArTh+qoX6RDUSe6VzpxXmKCSd_YaL-Hmex6ec5ExY-r_qRA@mail.gmail.com>

DPDK git baseline:
	Repo:dpdk-next-net-mlx, CommitID: 15a3e55fab2b184998cc2110d94421086f6c680e
	Repo:dpdk, CommitID: 6d7e741be18ab1e6ecce46edb2516318305c3c73


* Repo: dpdk-next-net-mlx
This will be required in git-pw 2.0
error: corrupt patch at line 11
Applying: doc/guides: Mention needed kernel option for mlx5 multiport e-switch
Patch failed at 0001 doc/guides: Mention needed kernel option for mlx5 multiport e-switch
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".

* Repo: dpdk
This will be required in git-pw 2.0
error: corrupt patch at line 11
Applying: doc/guides: Mention needed kernel option for mlx5 multiport e-switch
Patch failed at 0001 doc/guides: Mention needed kernel option for mlx5 multiport e-switch
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:[~2025-01-20 14:23 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='68906f$3aben5@ORVIESA003-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=4plague@gmail.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).