Skip to content

edk2: not apply patch with warning suppress if azl#10115

Merged
BettyRain merged 2 commits into3.0-devfrom
betty/edk2
Aug 12, 2024
Merged

edk2: not apply patch with warning suppress if azl#10115
BettyRain merged 2 commits into3.0-devfrom
betty/edk2

Conversation

@BettyRain
Copy link
Copy Markdown
Contributor

@BettyRain BettyRain commented Aug 12, 2024

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

What does the PR accomplish, why was it needed?
Add new condition to not apply patch with warning suppress if azl

Change Log
  • Add new condition to not apply patch with warning suppress if azl
Does this affect the toolchain?

NO

Test Methodology

Comment thread SPECS/edk2/edk2.spec Outdated
@BettyRain BettyRain merged commit 9ccf3dc into 3.0-dev Aug 12, 2024
@BettyRain BettyRain deleted the betty/edk2 branch August 12, 2024 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants