From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Chao Li <lichao@loongson.cn>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Gao, Liming" <gaoliming@byosoft.com.cn>
Subject: Re: [PATCH v1 14/34] .python/SpellCheck: Add "Loongson" and "LOONGARCH" to "words" section
Date: Fri, 9 Sep 2022 17:14:21 +0000 [thread overview]
Message-ID: <CO1PR11MB49290D70DA5BD91C222AFAD2D2439@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220908045024.1191094-1-lichao@loongson.cn>
Reviewed-by: Michael D Kinney <michael.d.kinney@intel.com>
> -----Original Message-----
> From: Chao Li <lichao@loongson.cn>
> Sent: Wednesday, September 7, 2022 9:50 PM
> To: devel@edk2.groups.io
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Gao, Liming <gaoliming@byosoft.com.cn>
> Subject: [PATCH v1 14/34] .python/SpellCheck: Add "Loongson" and "LOONGARCH" to "words" section
>
> Add Loongson and LOONGARCH to "words" section in cspell.base.yaml file
> to avoid spelling check error.
>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
>
> Signed-off-by: Chao Li <lichao@loongson.cn>
> ---
> .pytool/Plugin/SpellCheck/cspell.base.yaml | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/.pytool/Plugin/SpellCheck/cspell.base.yaml b/.pytool/Plugin/SpellCheck/cspell.base.yaml
> index f0d5791876..92e65ec6f6 100644
> --- a/.pytool/Plugin/SpellCheck/cspell.base.yaml
> +++ b/.pytool/Plugin/SpellCheck/cspell.base.yaml
> @@ -289,6 +289,8 @@
> "unrecovered",
>
> "cmocka",
>
> "unenrolling",
>
> - "unconfigure"
>
> + "unconfigure",
>
> + "Loongson",
>
> + "LOONGARCH"
>
> ]
>
> }
>
> --
> 2.27.0
prev parent reply other threads:[~2022-09-09 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 4:50 [PATCH v1 14/34] .python/SpellCheck: Add "Loongson" and "LOONGARCH" to "words" section Chao Li
2022-09-09 17:14 ` Michael D Kinney [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=CO1PR11MB49290D70DA5BD91C222AFAD2D2439@CO1PR11MB4929.namprd11.prod.outlook.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