Fix retry logic in UFS device detection APIs#1577
Fix retry logic in UFS device detection APIs#1577NishanthSanjeevi wants to merge 4 commits intomicrosoft:release/202502from
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release/202502 #1577 +/- ##
=================================================
Coverage ? 1.55%
=================================================
Files ? 637
Lines ? 234397
Branches ? 370
=================================================
Hits ? 3649
Misses ? 230735
Partials ? 13
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
makubacki
left a comment
There was a problem hiding this comment.
It would be preferable to have more granular error codes, but looking through the UFS code, they're all mixed up, so this seems reasonable.
|
Also, please create a PR in edk2 (without the MU_CHANGE tags). We don't need to wait on it to merge this. |
|
@NishanthSanjeevi, please push the uncrustify update when you get a chance. I've set automerge so it will merge when that's done. |
|
This PR has been automatically marked as stale because it has not had activity in 60 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions. |
|
@NishanthSanjeevi, how would you like to proceed with this PR? |
Head branch was pushed to by a user without write access
Hi MIchael, |
Description
Fix the retry logic in the UFS device detection APIs
How This Was Tested
Tested on physical Hardware
Integration Instructions
N/A