From: sys_stv@intel.com
To: test-report@dpdk.org, bruce.richardson@intel.com
Subject: compilation|WARNING| pw(155383) sid(35256) job(PER_PATCH_BUILD16214)[v4, 9/9] eal: simplify handling of conflicting cmdline options
Date: 21 Jul 2025 08:17:21 -0700 [thread overview]
Message-ID: <4653da$4njeoe@orviesa007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/155383
_apply issues_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: 2025-07-21 15:08:42
Reply_mail: <20250721150843.2737763-11-bruce.richardson@intel.com>
DPDK git baseline:
Repo:dpdk, CommitID: 2f4cd1b4dbaec6633da510da67c2213cfd2bd359
* Repo: dpdk
Server version missing
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: patch failed: lib/argparse/rte_argparse.c:508
error: lib/argparse/rte_argparse.c: patch does not apply
error: patch failed: lib/argparse/rte_argparse.h:60
error: lib/argparse/rte_argparse.h: patch does not apply
Applying: eal: add long options for each short option
Applying: argparse: add support for string and boolean args
Patch failed at 0002 argparse: add support for string and boolean args
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-07-21 15:17 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='4653da$4njeoe@orviesa007-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=bruce.richardson@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).