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

[edk2 rebase - task 2] Verify if commits with concerns should be applied or not #433

Closed
miczyg1 opened this issue Apr 28, 2023 · 3 comments

Comments

@miczyg1
Copy link
Contributor

miczyg1 commented Apr 28, 2023

Here is a list containing a diff against the upstream edk2:
https://paste.dasharo.com/?15d7c69a16f148ca#HA1yxMydgvQtGa7pac1RwitbZFGcahyNdHRig6x67cty)

I have marked each commit (on the begining of the line) with a symbol:

  • + means a commit that has to be cherry-picked onto a rebased edk2 branch (to be migrated)
  • - measn a commit has to be skipped/dropped
  • ?+ means a commit that SHOULD be cherry-picked onto a rebased edk2 branch (to be migrated), however there are some concerns which have to be checked first before deciding (the concerns are at the end of the line in parentheses)
  • ?- means a commit that SHOULD be skipped/dropped, however there are some concerns which have to be checked first before deciding (the concerns are at the end of the line in parentheses)
  • U means upstreamable fix to edk2-devel ML

There are also commits marked for quashing or to be migrated to DasharoModulePkg to make future rebases easier.

Next (second) task is to check the items makred with ?+ and ?- and verify whether the concerns to those commits apply, or if we change some suspicious part of given commit, it will stil lwork as expected or even fix some bugs. The test should be done on the current code base. The goal is to determine whether given commit:

  • ?- can be really dropped or needs some work to be fixed and then applied
  • ?+ is still needed (if not can be dropped) or needs some work to be fixed and then applied

The action to be taken is really dependent on the given commit and the concerns it has. Concerns should be tested on separate branches. If there are any positive results, a PR should be created. Then we should add new commits to paste created in task 1 and mark them for squashing with the commit it relates to, giving a + sybmol to it and removing the concern in parentheses. It will allow us to reduce the number of unneeded commits and clean up the list of unsure commits.

@miczyg1
Copy link
Contributor Author

miczyg1 commented May 6, 2023

?- 56313ac56f MdeModulePkg/Usb/Keyboard.c: don't request protocol before setting
?- 143d9fea48 MdeModulePkg/Usb/Keyboard.c: remove Get/SetConfig calls

Are actually correct... They help with USB USB transfer timeouts. ALso the drivers support only the boot protocol, so trying anything else is pointless in edk2.

@miczyg1
Copy link
Contributor Author

miczyg1 commented Oct 17, 2023

@SergiiDmytruk
Copy link
Member

Done: Dasharo/edk2#129 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants