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

Add definition of low-priority and high-priority RAS event from AIA #234

Merged
merged 1 commit into from
Feb 27, 2024

Conversation

YenHaoChen
Copy link
Contributor

Add definition of low-priority and high-priority RAS event from AIA.
image

@codecov-commenter
Copy link

codecov-commenter commented Feb 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.83%. Comparing base (275f72a) to head (4bb0ff4).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #234   +/-   ##
=======================================
  Coverage   92.83%   92.83%           
=======================================
  Files           3        3           
  Lines         642      642           
=======================================
  Hits          596      596           
  Misses         46       46           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@aswaterman
Copy link
Member

Let's change these to RAS_LOW_PRIO and RAS_HIGH_PRIO. The rationale is that RAS is the important part and priority is the less-important part, so RAS should come first in the name.

@YenHaoChen
Copy link
Contributor Author

@aswaterman Change the name as suggested

@aswaterman aswaterman merged commit f7c7181 into riscv:master Feb 27, 2024
2 checks passed
@YenHaoChen YenHaoChen deleted the pr-ras branch February 27, 2024 01:21
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.

3 participants