Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs/license.md: Update to BSD-2-Clause-Patent license #190

Merged

Conversation

makubacki
Copy link
Member

Updates the license for the documentation to be BSD-2-Clause-Patent
instead of BSD 2-Clause for consistency with /License.txt and most
of the content in Project Mu repositories.

Updates the license for the documentation to be BSD-2-Clause-Patent
instead of BSD 2-Clause for consistency with /License.txt and most
of the content in Project Mu repositories.

Signed-off-by: Michael Kubacki <[email protected]>
@makubacki makubacki added the semver:patch Pull requests that should increment the release patch version label Jan 23, 2024
@makubacki makubacki self-assigned this Jan 23, 2024
@makubacki makubacki merged commit 77fc535 into microsoft:master Jan 23, 2024
5 checks passed
julorenz117 pushed a commit to julorenz117/mu that referenced this pull request Aug 19, 2024
…tions (microsoft#190)

## Description

The MemoryProtectionExceptionHandlerLib only had an X64 implementation
before this PR. To enable memory protections for AARCH64, this library
needs an AARCH64 implementation.

- [x] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [x] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
    flow, or firmware?
  - Examples: Crypto algorithm change, buffer overflow fix, parameter
    validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
    in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
    a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
  - **Tests** - Does the change include any explicit test code?
  - Examples: Unit tests, integration tests, robot tests, ...
- [x] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
    outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
    on an a separate Web page, ...

## How This Was Tested

Running on Q35 and SBSA

## Integration Instructions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver:patch Pull requests that should increment the release patch version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants