From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <lichao@loongson.cn>
Cc: <spbrogan@outlook.com>
Subject: 回复: [edk2-devel] 回复: edk2-devel] Some questions about Azure CI
Date: Sun, 24 Apr 2022 08:51:03 +0800 [thread overview]
Message-ID: <004c01d85775$66020c30$32062490$@byosoft.com.cn> (raw)
In-Reply-To: <3631883D-61F4-43B6-BFBD-B37C74C065F3@getmailspring.com>
[-- Attachment #1: Type: text/plain, Size: 2693 bytes --]
Chao:
You can to add them ECC exception list in MdePkg\MdePkg.ci.yaml if they are all defined in MdePkg.
Thanks
Liming
发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Chao Li
发送时间: 2022年4月21日 16:53
收件人: "gaoliming" <gaoliming@byosoft.com.cn>
抄送: devel@edk2.groups.io; spbrogan@outlook.com
主题: Re: [edk2-devel] 回复: edk2-devel] Some questions about Azure CI
Hi Liming,
For Q2, all ECC errors is come from register naming. I think what you are pointing out is not UEFI SPEC, we have the LoongArch ISA manual on GitHub where 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?
LoongArch ISA manual link: https://loongson.github.io/LoongArch-Documentation/LoongArch-Vol1-EN.html <https://link.getmailspring.com/link/3631883D-61F4-43B6-BFBD-B37C74C065F3@getmailspring.com/0?redirect=https%3A%2F%2Floongson.github.io%2FLoongArch-Documentation%2FLoongArch-Vol1-EN.html&recipient=ZGV2ZWxAZWRrMi5ncm91cHMuaW8%3D>
Hope you reply, thank you!
--
Thanks,
Chao
------------------------
On 4月 20 2022, at 7:39 早上, "gaoliming" <gaoliming@byosoft.com.cn <mailto:gaoliming@byosoft.com.cn> > wrote:
For Q2, if key word is defined in public spec, they can be handled as the exception. You can see MdePkg\MdePkg.ci.yaml EccCheck section that has ExceptionList and IgnoreFiles.
Thanks
Liming
发件人: devel@edk2.groups.io <mailto:devel@edk2.groups.io> <devel@edk2.groups.io <mailto:devel@edk2.groups.io> > 代表 Sean
发送时间: 2022年4月20日 0:39
收件人: Chao Li <lichao@loongson.cn <mailto:lichao@loongson.cn> >; devel@edk2.groups.io <mailto:devel@edk2.groups.io>
主题: Re: [edk2-devel] Some questions about Azure CI
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 II Code Formatting · tianocore/tianocore.github.io Wiki <https://link.getmailspring.com/link/3631883D-61F4-43B6-BFBD-B37C74C065F3@getmailspring.com/1?redirect=https%3A%2F%2Fgithub.com%2Ftianocore%2Ftianocore.github.io%2Fwiki%2FEDK-II-Code-Formatting&recipient=ZGV2ZWxAZWRrMi5ncm91cHMuaW8%3D>
Q2 - New code additions require passing ECC. You will just need to work through the reported errors.
Thanks
Sean
<https://link.getmailspring.com/open/3631883D-61F4-43B6-BFBD-B37C74C065F3@getmailspring.com?me=a03b887c&recipient=ZGV2ZWxAZWRrMi5ncm91cHMuaW8%3D>
[-- Attachment #2: Type: text/html, Size: 10382 bytes --]
prev parent reply other threads:[~2022-04-24 0:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 4:42 Some questions about Azure CI Chao Li
2022-04-19 16:39 ` [edk2-devel] " Sean
2022-04-19 16:43 ` Rebecca Cran
2022-04-19 19:41 ` Michael Kubacki
2022-04-19 20:52 ` Michael D Kinney
2022-04-19 22:15 ` Michael Kubacki
2022-04-19 23:43 ` Michael Kubacki
2022-04-20 1:46 ` Chao Li
2022-04-20 1:56 ` Michael Kubacki
2022-04-20 10:10 ` Chao Li
2022-04-20 11:08 ` Chao Li
2022-04-20 14:45 ` Michael Kubacki
2022-04-21 1:34 ` Chao Li
[not found] ` <16E7C575D2AAB8FB.27458@groups.io>
2022-05-16 5:15 ` Chao Li
2022-05-16 16:12 ` Michael Kubacki
2022-05-23 1:46 ` Chao Li
2022-09-06 14:14 ` 回复:Re: " Chao Li
2022-09-06 18:31 ` Michael D Kinney
2022-04-20 1:59 ` Michael Kubacki
2022-04-19 23:39 ` 回复: " gaoliming
2022-04-21 8:52 ` 回复: edk2-devel] " Chao Li
2022-04-24 0:51 ` gaoliming [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-list 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='004c01d85775$66020c30$32062490$@byosoft.com.cn' \
--to=devel@edk2.groups.io \
/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