Open
Conversation
Add support for MADT table flags. Currently the ACPI spec only defines the PCAT_COMPAT flag. Signed-off-by: Luiz Aoqui <lgfa29@gmail.com>
lgfa29
requested review from
jiangliu,
liuw,
rbradford and
sboeuf
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add support for MADT table flags. Currently the ACPI spec only defines the
PCAT_COMPATflag.Summary of the PR
Table 5.20 of the ACPI spec. defines the flags that can be set for the MADT table, but currently it's not possible to set them. This PR adds support for defining MADT table flags (currently only
PCAT_COMPATexists).Requirements
Before submitting your PR, please make sure you addressed the following
requirements:
git commit -s), and the commit message has max 60 characters for thesummary and max 75 characters for each description line.
test.
Release" section of CHANGELOG.md (if no such section exists, please create one).
unsafecode is properly documented.Note: I'm not sure where to find the
CHANGELOG.mdfile.