-
Notifications
You must be signed in to change notification settings - Fork 163
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
Implement additional BootServices
functions
#550
Changes from all commits
1855be5
89688e6
94b5ee1
4d6aabe
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,7 @@ | ||
#![no_std] | ||
#![no_main] | ||
#![feature(abi_efiapi)] | ||
#![feature(negative_impls)] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I can't see why this is required. Can you please give some details? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, Specifically in /// Dummy protocol for tests
#[unsafe_guid("1a972918-3f69-4b5d-8cb4-cece2309c7f5")]
#[derive(Protocol)]
struct TestProtocol {} There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Alright, thanks for the pointer. What does @nicholasbishop say? Is this fine? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this is fine, just a consequence of the way we implement protocols. (There's a little bit of commentary on |
||
|
||
#[macro_use] | ||
extern crate log; | ||
|
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.
nit: These changes could be squashed with the commit(s) where the changes were introduced.
However, this is not a hard requirement.
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 need to learn git a bit better anyway, so I'll see what I can do about cleaning up the history a bit today.
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.
👍 Moving things between existing git commits is kinda hard without experience. In the last months, I've spent some time on improving my skills. The following workflow worked for me. Maybe it helps you as well, hopefully:
git rebase --interactive HEAD~4
(for four commits)e
/edit
cargo fmt
&&cargo clippy
plusgit add
all changesgit rebase --continue
Ideally, git should discard the "code style only commit" if you can pull these changes into earlier commits this way. Let me know what worked for you! :)
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.
That actually was a really easy way to understand how to split commits apart, thanks! I had no idea that git would detect and let you remove empty commits.