From: sys_stv@intel.com
To: test-report@dpdk.org, alan.elder@microsoft.com
Subject: compilation|WARNING| pw(139282) sid(31741) job(PER_PATCH_BUILD11678)[v4] net/netvsc: fix number Tx queues > Rx queues
Date: 15 Apr 2024 07:48:00 -0700 [thread overview]
Message-ID: <7f45a9$p8oli@fmviesa003-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/139282
_apply issues_
Submitter: Alan Elder <alan.elder@microsoft.com>
Date: 2024-04-15 14:40:44
Reply_mail: <PA4PR83MB05261AB024A2F6A286CBF22E97092@PA4PR83MB0526.EURPRD83.prod.outlook.com>
DPDK git baseline:
Repo:dpdk-next-net, CommitID: ea9b0f7277acc931ced3fee4a3ee087a26ee1401
Repo:dpdk, CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
* Repo: dpdk-next-net
This will be required in git-pw 2.0
error: patch fragment without header at line 24: @@ -301,6 +313,27 @@ hn_dev_tx_queue_setup(struct rte_eth_dev *dev,
Applying: net/netvsc: fix number Tx queues > Rx queues
Patch failed at 0001 net/netvsc: fix number Tx queues > Rx queues
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: patch fragment without header at line 24: @@ -301,6 +313,27 @@ hn_dev_tx_queue_setup(struct rte_eth_dev *dev,
Applying: net/netvsc: fix number Tx queues > Rx queues
Patch failed at 0001 net/netvsc: fix number Tx queues > Rx queues
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:[~2024-04-15 14:48 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='7f45a9$p8oli@fmviesa003-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=alan.elder@microsoft.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).