<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Patrick,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
> But, what authorization are you referring to, for modifying the build</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
> options? Do you mean it needs to be authorized by DPDK maintainers, or</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
> by the CI community, or by someone at Intel STV team?</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
This requires authorization from DPDK community maintainers.</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
> Why it is being used on your end. What are the "predictable risks?"</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Sorry, this build option has been in our CI system for a long time.</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
And removing this option would pose unpredictable risks.</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The next dpdk cycle is approaching, and in order to maintain the stability of the CI environment, the settings of the CI system cannot be modified arbitrarily.</div>
<div id="appendonsend"></div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Tingting Liao</div>
<hr style="display: inline-block; width: 98%;">
<div id="divRplyFwdMsg" dir="ltr"><span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><b>发件人:</b> Patrick Robb <probb@iol.unh.edu><br>
<b>发送时间:</b> 2024年8月8日 20:37<br>
<b>收件人:</b> Liao, TingtingX <tingtingx.liao@intel.com><br>
<b>抄送:</b> Juraj Linkeš <juraj.linkes@pantheon.tech>; Xu, HailinX <hailinx.xu@intel.com>; Cui, KaixinX <kaixinx.cui@intel.com>; ci@dpdk.org <ci@dpdk.org><br>
<b>主题:</b> Re: compilation|FAILURE| pw(142339) sid(32483) job(PER_PATCH_BUILD12580)[v8, 5/5] dts: add API doc generation</span>
<div> </div>
</div>
<div style="font-size: 11pt;">On Wed, Aug 7, 2024 at 11:28 PM Liao, TingtingX<br>
<tingtingx.liao@intel.com> wrote:<br>
><br>
> Hi Juraj,<br>
><br>
> Sorry, we cannot modify the parameters of CI apply patch without authorization.<br>
> The doc directory is used to store documents and does not support code submission.<br>
> Based on the special circumstances of your patch, you can directly contact the community maintainer to decide whether to merge this patch.<br>
><br>
<br>
Okay, I agree that if needed we can just talk to the maintainers, do a<br>
manual test for this patch, and they can merge based on the results of<br>
manual testing.<br>
<br>
But, what authorization are you referring to, for modifying the build<br>
options? Do you mean it needs to be authorized by DPDK maintainers, or<br>
by the CI community, or by someone at Intel STV team? We are not using<br>
this build option at the UNH CI testing lab, which is why I want to<br>
understand better why it is being used on your end. What are the<br>
"predictable risks?"<br>
<br>
Sorry for taking up your time. I also want to make sure that we at UNH<br>
are not using a bad process!</div>
</body>
</html>