-
-
Notifications
You must be signed in to change notification settings - Fork 191
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
boards, module and Makefile: drop iotools #1707
Conversation
@macpijan This was the only use of iotools right? If so please remove modules/iotools and the bits from Makefile |
I removed it at first. @tlaurion Said it was not the only user of it, now I am confused: #1704 (comment) Perhaps you meant I should remove it from these as well?
? |
@JonathonHall-Purism yes. no more iotools calls in codebase outside of initrd/bin/nitropad-shutdown.sh which vanished under #1704 |
Sorry. What I meant is that boards, mostly testing boards (qemu) where referencing it (including it for testing purposes) while if the modules vanishes and boards still referring to it, they would break at builds. TLDR: all references to IOTOOLS need to disappear, including Makefile conditional inclusion. Makes sense?
|
Renamed PR to match goal, will close #1706 |
As discussed in: linuxboot#1704 there is no need to include iotools module for nitropads. Since there is no board using it, and we see no reason to use it in the future (the EC udpate will not require it, as update will be server by coreboot in the future), drop the module as well. Signed-off-by: Maciej Pijanowski <[email protected]>
0b5fea1
to
2cd5b09
Compare
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.
LGTM, thanks 🙇
@macpijan thanks for contributing upstream! Much appreciated!!!!!! Merging |
As discussed in: #1704
there is no need to include iotools module for nitropads.