From: "Laszlo Ersek" <lersek@redhat.com>
To: mikuback@linux.microsoft.com, devel@edk2.groups.io
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Rebecca Cran <rebecca@bsdio.com>,
Peter Grehan <grehan@freebsd.org>
Subject: Re: [PATCH v1 4/4] OvmfPkg: Do not check VbeShim.h formatting with Uncrustify
Date: Tue, 22 Mar 2022 07:35:40 +0100 [thread overview]
Message-ID: <3c0d084f-788f-6737-9df2-a02456c4137d@redhat.com> (raw)
In-Reply-To: <20220322015814.9182-5-mikuback@linux.microsoft.com>
On 03/22/22 02:58, mikuback@linux.microsoft.com wrote:
> From: Michael Kubacki <michael.kubacki@microsoft.com>
>
> REF:https://bugzilla.tianocore.org/show_bug.cgi?id=3875
>
> The following files:
> OvmfPkg/Bhyve/BhyveRfbDxe/VbeShim.h
> OvmfPkg/QemuVideoDxe/VbeShim.h
>
> Are auto generated by the following generators:
> OvmfPkg/Bhyve/BhyveRfbDxe/VbeShim.sh
> OvmfPkg/QemuVideoDxe/VbeShim.sh
>
> Therefore, Uncrustify causes a file update to produce a very large
> diff due to formatting changes.
>
> This change does the following:
> 1. Reverts the Uncrustify changes applied to the files in commit
> ac0a286f4d74.
> 2. Uses a new UncrustifyCheck CI plugin configuration option to
> exclude the files from future formatting checks.
>
> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: Rebecca Cran <rebecca@bsdio.com>
> Cc: Peter Grehan <grehan@freebsd.org>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
> ---
> OvmfPkg/OvmfPkg.ci.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/OvmfPkg/OvmfPkg.ci.yaml b/OvmfPkg/OvmfPkg.ci.yaml
> index 7459b84d8090..ff022242b018 100644
> --- a/OvmfPkg/OvmfPkg.ci.yaml
> +++ b/OvmfPkg/OvmfPkg.ci.yaml
> @@ -97,5 +97,10 @@
> ], # words to extend to the dictionary for this package
> "IgnoreStandardPaths": [], # Standard Plugin defined paths that should be ignore
> "AdditionalIncludePaths": [] # Additional paths to spell check (wildcards supported)
> + },
> +
> + # options defined in .pytool/Plugin/UncrustifyCheck
> + "UncrustifyCheck": {
> + "IgnoreFiles": ["VbeShim.h"]
> }
> }
>
Acked-by: Laszlo Ersek <lersek@redhat.com>
(Didn't expect the plugin / new option to take relative pathnames / last
components as well, but it's very handy in this case.)
Thanks
Laszlo
next prev parent reply other threads:[~2022-03-22 6:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 1:58 [PATCH v1 0/4] UncrustifyCheck Ignore Support Michael Kubacki
2022-03-22 1:58 ` [PATCH v1 1/4] .pytool/Plugin/UncrustifyCheck: Update func to return absolute paths Michael Kubacki
2022-03-22 16:07 ` [edk2-devel] " Michael D Kinney
2022-03-22 16:12 ` Michael D Kinney
2022-04-01 16:22 ` Michael Kubacki
2022-03-22 1:58 ` [PATCH v1 2/4] .pytool/Plugin/UncrustifyCheck: Add ignore file support Michael Kubacki
2022-03-22 16:14 ` Michael D Kinney
2022-04-01 16:07 ` [edk2-devel] " Michael Kubacki
2022-04-01 16:50 ` Michael D Kinney
2022-04-01 17:45 ` Sean
2022-04-03 17:32 ` Michael D Kinney
2022-03-22 1:58 ` [PATCH v1 3/4] OvmfPkg: Revert Uncrustify formatting in VbeShim.h files Michael Kubacki
2022-03-22 6:34 ` Laszlo Ersek
2022-03-22 8:45 ` [edk2-devel] " Gerd Hoffmann
2022-03-22 1:58 ` [PATCH v1 4/4] OvmfPkg: Do not check VbeShim.h formatting with Uncrustify Michael Kubacki
2022-03-22 6:35 ` Laszlo Ersek [this message]
2022-03-22 8:46 ` [edk2-devel] " Gerd Hoffmann
2022-03-22 16:14 ` [PATCH v1 0/4] UncrustifyCheck Ignore Support Michael D Kinney
2022-04-01 16:04 ` [edk2-devel] " Michael Kubacki
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=3c0d084f-788f-6737-9df2-a02456c4137d@redhat.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