From: Bruce Richardson <bruce.richardson@intel.com>
To: "Liao, TingtingX" <tingtingx.liao@intel.com>
Cc: "sys_stv@intel.com" <sys_stv@intel.com>,
"test-report@dpdk.org" <test-report@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>,
"Xu, HailinX" <hailinx.xu@intel.com>,
"Cui, KaixinX" <kaixinx.cui@intel.com>
Subject: Re: compilation|FAILURE| pw(150284) sid(34398) job(PER_PATCH_BUILD14646)[v5, 25/25] net/intel/common: extract common Rx vector criteria
Date: Tue, 21 Jan 2025 08:44:56 +0000 [thread overview]
Message-ID: <Z49eiPOZGYzb5y0u@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <PH7PR11MB68599660461491D94C5A416092E62@PH7PR11MB6859.namprd11.prod.outlook.com>
On Tue, Jan 21, 2025 at 02:26:59AM +0000, Liao, TingtingX wrote:
> Sorry. There is no error with this series.
>
> The error is caused by the CI doesn't apply any changes with doc/*.
>
> Community decided to exclude doc/*, as doc/* change frequently,
> especially the release notes, cause a lot of conflict with main tree.
>
I believe it was apply conflicts on the release notes was the major cause
of issues, so perhaps we can change the Intel CI to skip release notes
application rather than all doc changes. The majority of doc changes should
be fine.
/Bruce
prev parent reply other threads:[~2025-01-21 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45c20e$42via9@orviesa002-auth.jf.intel.com>
2025-01-21 2:26 ` Liao, TingtingX
2025-01-21 8:44 ` Bruce Richardson [this message]
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=Z49eiPOZGYzb5y0u@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hailinx.xu@intel.com \
--cc=kaixinx.cui@intel.com \
--cc=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=tingtingx.liao@intel.com \
/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).