public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: Ard Biesheuvel <ardb@kernel.org>, devel@edk2.groups.io
Cc: quic_rcran@quicinc.com, quic_llindhol@quicinc.com,
	Michael Kinney <michael.d.kinney@intel.com>,
	Andrew Fish <afish@apple.com>,
	Sami Mujawar <sami.mujawar@arm.com>,
	Jian J Wang <jian.j.wang@intel.com>,
	Liming Gao <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] [PATCH v2 1/2] ArmPkg: implement EFI_MP_SERVICES_PROTOCOL based on PSCI calls
Date: Wed, 7 Sep 2022 11:32:47 -0400	[thread overview]
Message-ID: <acef1186-b716-a297-53d4-b1fb48b3e5fc@linux.microsoft.com> (raw)
In-Reply-To: <CAMj1kXGe9vJwJSJ2Fj9QWzAuBW3XJxXDpKd3hUc4ZQ=Eu3SpeA@mail.gmail.com>

Please note that I already turned AuditOnly mode on for the EmbeddedPkg 
patch series.

On 9/7/2022 11:21 AM, Ard Biesheuvel wrote:
> On Wed, 7 Sept 2022 at 17:11, Michael Kubacki
> <mikuback@linux.microsoft.com> wrote:
>>
>> Maintainers have two options for Spell Check as described in the Spell
>> Check CI Plugin readme -
>> https://github.com/tianocore/edk2/tree/master/.pytool/Plugin/SpellCheck
>>
>> 1. Set AuditOnly to "true" - Disables all spelling errors in the package
>> from the failing the build entirely.
>>
>> 2. Extend the dictionary - Add specific words that are allowed. Many
>> packages already do this.
>>
>> 3. IgnoreStandardPaths - Do not check files by path pattern.
>>
>> As a maintainer, you can either opt out of Spell Check from the failing
>> the build entirely by enabling AuditOnly or choose a different level of
>> granularity by simply updating your package CI YAML file.
>>
> 
> Thanks for the explanation - patch coming up.
> 
> 
>> On 9/7/2022 3:35 AM, Ard Biesheuvel wrote:
>>> On Wed, 7 Sept 2022 at 06:35, Rebecca Cran <quic_rcran@quicinc.com> wrote:
>>>>
>>>> Also, CI is failing in the SpellCheck test because of the
>>>> "-mstrict-align" in
>>>> ArmPsciMpServicesDxe.inf.
>>>>
>>>> /home/vsts/work/1/s/ArmPkg/Drivers/ArmPsciMpServicesDxe/ArmPsciMpServicesDxe.inf:55:25
>>>> - Unknown word (mstrict)
>>>>
>>>> Should I add "mstrict" to pytool/Plugin/SpellCheck/cspell.base.yaml ?
>>>>
>>>
>>> This is getting ridiculous.
>>>
>>> I'm all for code quality and automation, but if t we cannot use
>>> compiler command line options that it supported since the dawn of time
>>> without bending over backwards to placate the CI machine, we are
>>> throwing out the baby with the bath water.
>>>
>>> At the very least, maintainers should be able to override the CI - I
>>> spent 2 hours yesterday preparing a submission that ultimately got
>>> rejected because MPIDR is not in the permitted word list (suggestion:
>>> use 'mpidr')
>>>
>>> In the Linux kernel, we have patch check and sparse (which is somewhat
>>> similar to ECC in a sense). Some maintainers run it, some don't, but
>>> in the end, the discretion lies with the person not the machine. This
>>> is the only way that makes sense.
>>>
>>> As the co-maintainer of ArmPkg, ArmVirtPkg, ArmPlatformPkg, OvmfPkg
>>> and EmbeddedPkg, I hereby request that the Ci restrictions are either
>>> lifted entirely for these packages, or relaxed so that a PR can be
>>> merged at my discretion, even if the CI thinks there are unresolved
>>> issues.
>>>
>>>
>>>
>>>> On 9/6/22 22:25, Rebecca Cran wrote:
>>>>> On 9/6/22 22:03, Rebecca Cran wrote:
>>>>>> diff --git a/ArmPkg/ArmPkg.dsc b/ArmPkg/ArmPkg.dsc
>>>>>> index 59fd8f295d4f..4716789402fc 100644
>>>>>> --- a/ArmPkg/ArmPkg.dsc
>>>>>> +++ b/ArmPkg/ArmPkg.dsc
>>>>>> @@ -125,6 +125,7 @@ [Components.common]
>>>>>>       ArmPkg/Drivers/CpuPei/CpuPei.inf
>>>>>>       ArmPkg/Drivers/ArmGic/ArmGicDxe.inf
>>>>>>       ArmPkg/Drivers/ArmGic/ArmGicLib.inf
>>>>>> +  ArmPkg/Drivers/ArmPsciMpServicesDxe/ArmPsciMpServicesDxe.inf
>>>>>>       ArmPkg/Drivers/GenericWatchdogDxe/GenericWatchdogDxe.inf
>>>>>>       ArmPkg/Drivers/TimerDxe/TimerDxe.inf
>>>>> This won't work, since there's no support for 32-bit ARM code.
>>>>> I'll move it into the AARCH64 section.
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>> 
>>
>>

  reply	other threads:[~2022-09-07 15:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07  4:03 [PATCH v2 0/2] Add support EFI_MP_SERVICES_PROTOCOL on AARCH64 Rebecca Cran
2022-09-07  4:03 ` [PATCH v2 1/2] ArmPkg: implement EFI_MP_SERVICES_PROTOCOL based on PSCI calls Rebecca Cran
2022-09-07  4:25   ` Rebecca Cran
     [not found]   ` <1712796FB27A1CB6.17907@groups.io>
2022-09-07  4:35     ` [edk2-devel] " Rebecca Cran
2022-09-07  4:38       ` Michael Kubacki
2022-09-07  7:35       ` Ard Biesheuvel
2022-09-07 15:11         ` Michael Kubacki
2022-09-07 15:21           ` Ard Biesheuvel
2022-09-07 15:32             ` Michael Kubacki [this message]
2022-09-07  8:13   ` Ard Biesheuvel
2022-09-21 13:08     ` Rebecca Cran
2022-09-07  4:03 ` [PATCH v2 2/2] MdeModulePkg: Add new Application/MpServicesTest application Rebecca Cran

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=acef1186-b716-a297-53d4-b1fb48b3e5fc@linux.microsoft.com \
    --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