From: sys_stv@intel.com
To: test-report@dpdk.org, ming3.li@intel.com
Subject: compilation|WARNING| pw(134811) sid(30443) job(PER_PATCH_BUILD10262)[v4] windows/virt2phys: fix block MDL not updated
Date: 04 Dec 2023 03:53:37 -0800 [thread overview]
Message-ID: <8536f9$bca8e@orviesa002-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/134811
_apply issues_
Submitter: Ric Li <ming3.li@intel.com>
Date: 2023-12-04 10:32:14
Reply_mail: <20231204103214.2504017-1-ming3.li@intel.com>
DPDK git baseline:
Repo:dpdk, CommitID: c858f006d1f7161986c88847259a400d8f80d81b
* Repo: dpdk
error: windows/virt2phys/virt2phys.c: does not exist in index
error: windows/virt2phys/virt2phys_logic.c: does not exist in index
Applying: windows/virt2phys: fix block MDL not updated
Patch failed at 0001 windows/virt2phys: fix block MDL not updated
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:[~2023-12-04 11:53 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='8536f9$bca8e@orviesa002-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=ming3.li@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).