-
Notifications
You must be signed in to change notification settings - Fork 0
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
81 fault priority #147
base: develop
Are you sure you want to change the base?
81 fault priority #147
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait for @Sabramz review
return fault_status; | ||
|
||
// TODO: Remove This !!!! (because this is actually a non-critical fault?) | ||
// fault_status &= ~DISCHARGE_LIMIT_ENFORCEMENT_FAULT; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Sabramz hmmm should this be here or not
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not know. Something tells me this was a debugging thing done in a rush last year. Lets bring DCL fault back in, and if it gives us problems we can remove it easily.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like these changes.
Changes
is_critical
field in fault_eval_tacc_data_t
To Do
Checklist
It can be helpful to check the
Checks
andFiles changed
tabs.Please reach out to your Project Lead if anything is unclear.
Please request reviewers and ping on slack only after you've gone through this whole checklist.
Closes #81