From: Bruce Richardson <bruce.richardson@intel.com>
To: "Liao, TingtingX" <tingtingx.liao@intel.com>
Cc: "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(150482) sid(34444) job(PER_PATCH_BUILD14715)[v6, 25/25] net/intel: extract common Rx vector criteria
Date: Mon, 27 Jan 2025 14:37:55 +0000 [thread overview]
Message-ID: <Z5eaQ08xFXKRHsLt@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <PH7PR11MB6859FFC52948A6F81A23FF0292ED2@PH7PR11MB6859.namprd11.prod.outlook.com>
On Sun, Jan 26, 2025 at 01:45:54AM +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.
>
Can the Intel CI be changed to only exclude release notes changes rather
than all doc changes? Outside of the release notes, conflicts are not very
common.
Regards,
/Bruce
prev parent reply other threads:[~2025-01-27 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7206a3$36uj87@orviesa010-auth.jf.intel.com>
2025-01-26 1:45 ` Liao, TingtingX
2025-01-27 14:37 ` 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=Z5eaQ08xFXKRHsLt@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=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).