From: sys_stv@intel.com
To: test-report@dpdk.org, farhatullah.software.engr999@gmail.com
Subject: compilation|WARNING| pw(149410) sid(34218) job(PER_PATCH_BUILD14452)doc: fixing name of rfc2697 and rfc2698
Date: 23 Dec 2024 09:08:14 -0800 [thread overview]
Message-ID: <4bfdee$33cu4o@orviesa004-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/149410
_apply issues_
Submitter: Farhat Ullah <farhatullah.software.engr999@gmail.com>
Date: 2024-12-23 17:00:08
Reply_mail: <CAOE7cFB+U97a9ys6zHXFEKt=jEx+7ESCQkJgH7Crcjr0j2T1NQ@mail.gmail.com>
DPDK git baseline:
Repo:dpdk-next-net, CommitID: 7df61db6c387703a36306c1aea92225921e2eeb2
Repo:dpdk, CommitID: fd51012de5369679e807be1d6a81d63ef15015ce
* Repo: dpdk-next-net
This will be required in git-pw 2.0
error: patch fragment without header at line 6: @@ -2385,7 +2385,7 @@ where:
Applying: doc: fixing name of rfc2697 and rfc2698
Patch failed at 0001 doc: fixing name of rfc2697 and rfc2698
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 6: @@ -2385,7 +2385,7 @@ where:
Applying: doc: fixing name of rfc2697 and rfc2698
Patch failed at 0001 doc: fixing name of rfc2697 and rfc2698
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-12-23 17:08 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='4bfdee$33cu4o@orviesa004-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=farhatullah.software.engr999@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).