From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.byosoft.com.cn (mail.byosoft.com.cn [58.240.74.242]) by mx.groups.io with SMTP id smtpd.web12.12985.1650761479280808388 for ; Sat, 23 Apr 2022 17:51:21 -0700 Authentication-Results: mx.groups.io; dkim=missing; spf=none, err=permanent DNS error (domain: byosoft.com.cn, ip: 58.240.74.242, mailfrom: gaoliming@byosoft.com.cn) Received: from DESKTOPS6D0PVI ([101.224.116.119]) (envelope-sender ) by 192.168.6.13 with ESMTP for ; Sun, 24 Apr 2022 08:51:15 +0800 X-WM-Sender: gaoliming@byosoft.com.cn X-Originating-IP: 101.224.116.119 X-WM-AuthFlag: YES X-WM-AuthUser: gaoliming@byosoft.com.cn From: "gaoliming" To: , Cc: References: <015801d85446$ae0d22d0$0a276870$@byosoft.com.cn> <3631883D-61F4-43B6-BFBD-B37C74C065F3@getmailspring.com> In-Reply-To: <3631883D-61F4-43B6-BFBD-B37C74C065F3@getmailspring.com> Subject: =?UTF-8?B?5Zue5aSNOiBbZWRrMi1kZXZlbF0g5Zue5aSNOiBlZGsyLWRldmVsXSBTb21lIHF1ZXN0aW9ucyBhYm91dCBBenVyZSBDSQ==?= Date: Sun, 24 Apr 2022 08:51:03 +0800 Message-ID: <004c01d85775$66020c30$32062490$@byosoft.com.cn> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQIxmYi1kU82t8A8hacb4mn7p684HwFVPPyprEENjIA= Content-Type: multipart/alternative; boundary="----=_NextPart_000_004D_01D857B8.74265DA0" Content-Language: zh-cn ------=_NextPart_000_004D_01D857B8.74265DA0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Chao: You can to add them ECC exception list in MdePkg\MdePkg.ci.yaml if they ar= e all defined in MdePkg.=20 =20 Thanks Liming =E5=8F=91=E4=BB=B6=E4=BA=BA: devel@edk2.groups.io = =E4=BB=A3=E8=A1=A8 Chao Li =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2022=E5=B9=B44=E6=9C=8821=E6=97=A5 16= :53 =E6=94=B6=E4=BB=B6=E4=BA=BA: "gaoliming" =E6=8A=84=E9=80=81: devel@edk2.groups.io; spbrogan@outlook.com =E4=B8=BB=E9=A2=98: Re: [edk2-devel] =E5=9B=9E=E5=A4=8D: edk2-devel] Some q= uestions about Azure CI =20 Hi Liming, =20 For Q2, all ECC errors is come from register naming. I think what you are p= ointing out is not UEFI SPEC, we have the LoongArch ISA manual on GitHub wh= ere all of register naming are defined. Dose that means it is a public SPEC= ? If yes, what should I do to get the Azure CI ECC to pass? =20 LoongArch ISA manual link: https://loongson.github.io/LoongArch-Documentati= on/LoongArch-Vol1-EN.html =20 =20 Hope you reply, thank you! =20 -- Thanks, Chao ------------------------ =20 On 4=E6=9C=88 20 2022, at 7:39 =E6=97=A9=E4=B8=8A, "gaoliming" > wrote: For Q2, if key word is defined in public spec, they can be handled as the e= xception. You can see MdePkg\MdePkg.ci.yaml EccCheck section that has Exce= ptionList and IgnoreFiles. =20 =20 =20 Thanks =20 Liming =20 =E5=8F=91=E4=BB=B6=E4=BA=BA: devel@edk2.groups.io > =E4=BB=A3=E8=A1= =A8 Sean =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2022=E5=B9=B44=E6=9C=8820=E6=97=A5 0:= 39 =E6=94=B6=E4=BB=B6=E4=BA=BA: Chao Li >; devel@edk2.groups.io =20 =E4=B8=BB=E9=A2=98: Re: [edk2-devel] Some questions about Azure CI =20 =20 Q1 - There should be more details in the actual log file, but your code has= formatting errors. In the last few months, the uncrusitfy tool has been = introduced to get common formatting errors fixed. See details here: EDK I= I Code Formatting =C2=B7 tianocore/tianocore.github.io Wiki = =20 =20 Q2 - New code additions require passing ECC. You will just need to work th= rough the reported errors.=20 =20 Thanks Sean =20 =20 ------=_NextPart_000_004D_01D857B8.74265DA0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Chao:

=C2=A0Y= ou can to add them ECC exception list in MdePkg\MdePkg.ci.yaml if they are = all defined in MdePkg.

&n= bsp;

Thanks

Liming

=E5=8F=91=E4=BB=B6=E4=BA=BA:= devel@edk2.groups.io <devel@edk2.groups.io> =E4=BB=A3=E8=A1=A8 Chao Li
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4= : 2022=E5=B9=B44=E6=9C=8821=E6=97=A5 16:53
=E6=94= =B6=E4=BB=B6=E4=BA=BA: &qu= ot;gaoliming" <gaoliming@byosoft.com.cn>
=E6=8A=84= =E9=80=81: devel@edk2.grou= ps.io; spbrogan@outlook.com
=E4=B8=BB=E9=A2=98: Re: [edk2-devel] =E5=9B=9E=E5=A4= =8D: edk2-devel] Some questions about Azure CI

 

Hi Lim= ing,

 

For Q= 2, all ECC errors is come from register naming. I think what you are pointi= ng out is not UEFI SPEC, we have the LoongArch ISA manual on GitHub where a= ll of register naming are defined. Dose that means it is a public SPEC? If = yes, what should I do to get the Azure CI ECC to pass?

 

=

 

Hope you reply, thank you!

<= /div>

 

--
Thanks,
Chao
--------= ----------------

 

On 4=E6=9C=88 20 2022, at 7:39 = =E6=97=A9=E4=B8=8A, "gaoliming" <gaoliming@byosoft.com.cn> wrote:

For Q2, if key word is defined i= n public spec, they can be handled as the exception.  You can see MdeP= kg\MdePkg.ci.yaml EccCheck section that has ExceptionList and IgnoreFiles.<= /span>

<= span lang=3DEN-US> 

&= nbsp;

 

Thanks

 

Liming

 

=

=E5=8F=91=E4=BB=B6=E4=BA=BA: devel@edk2.groups.io <= devel@edk2.groups.io> =E4=BB=A3=E8=A1=A8 Sean<= /span>

=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2022=E5=B9=B44=E6=9C=8820=E6=97=A5 0:39

=E6=94=B6=E4=BB=B6=E4= =BA=BA: Chao Li <lichao@loongson.cn>; devel@edk2.groups.io

=E4=B8=BB=E9=A2=98: Re: [edk2-devel] Some questi= ons about Azure CI

 

 

Q1 - There sh= ould be more details in the actual log file, but your code has formatting e= rrors.   In the last few months, the uncrusitfy tool has been int= roduced to get common formatting errors fixed.   See details here= : EDK II Code Formatting =C2= =B7 tianocore/tianocore.github.io Wiki

 

Q2 - New code additions require passing EC= C.  You will just need to work through the reported errors. =

 <= /o:p>

Thanks

Sean<= /o:p>

&n= bsp;

3D"Sent

------=_NextPart_000_004D_01D857B8.74265DA0--