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

Upstream resolved issue in DxeServicesLib for FvHandle being NULL #10

Merged

Conversation

spbrogan
Copy link
Member

Undo Project Mu change since upstream is now fixed.

@corthon corthon self-requested a review December 13, 2018 21:24
Copy link
Member

@corthon corthon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@spbrogan spbrogan merged commit 6de942e into release/201808 Dec 13, 2018
@spbrogan spbrogan deleted the personal/sebrogan/removeMsChangeDxeServices branch December 13, 2018 21:42
corthon pushed a commit that referenced this pull request Jan 22, 2019
corthon pushed a commit that referenced this pull request Mar 20, 2019
apop5 pushed a commit to apop5/mu_basecore that referenced this pull request Jan 2, 2025
This patch does not impact functionality. It aims to clarify the
synchronization flow between the BSP and APs to enhance code
readability and understanding:

Steps microsoft#6 and microsoft#11 are the basic synchronization requirements for all
cases.

Steps microsoft#1 is additional requirements if the MmCpuSyncModeTradition
mode is selected.

Steps microsoft#1, microsoft#2, microsoft#3, microsoft#4, microsoft#5, microsoft#7, microsoft#8, microsoft#9, and microsoft#10 are additional
requirements if the system needs to configure the MTRR.

Steps microsoft#9 and microsoft#10 are additional requirements if the system needs to
support the mSmmDebugAgentSupport.

Signed-off-by: Jiaxin Wu <jiaxin.wu@intel.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants