-
Notifications
You must be signed in to change notification settings - Fork 168
Better delay description #240
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
Conversation
CC #236 Signed-off-by: Daniel Egger <[email protected]>
r? @korken89 (rust_highfive has picked a reviewer for you, use r? to override) |
src/asm.rs
Outdated
/// NOTE that the delay can take much longer if interrupts are serviced during its execution. | ||
/// NOTE that the delay can take much longer if interrupts are serviced during its execution | ||
/// and the execution time may wary with other factors. This delay is mainly useful for simple | ||
/// timer-less initialisation of peripherals iff accurate timing is not essential. In any other |
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.
/// timer-less initialisation of peripherals iff accurate timing is not essential. In any other | |
/// timer-less initialization of peripherals if accurate timing is not essential. In any other |
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.
Hm, the iff is intended. I'm fine with changing the spelling to AE.
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.
Maybe expand it to "if and only if" then? iff tends to confuse people.
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.
Hm, I've never met anyone who was confused about that but sure, why not.
Co-authored-by: Jonas Schievink <[email protected]>
Signed-off-by: Daniel Egger <[email protected]>
Signed-off-by: Daniel Egger <[email protected]>
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.
bors r+
Build succeeded: |
249: More v0.6.3 backports r=jonas-schievink a=adamgreig I think this includes the remainder of the non-breaking changes since v0.6.2, with a couple of exceptions: * #240 seemed low-impact but had loads of separate commits to cherry-pick * #220 is I think non-breaking but was quite a substantial change, perhaps I could still include it ~~I did include #226 which adds a new field to `Peripherals`, but as I understand it that should be a non-breaking change since it's non-exhaustive.~~ I've updated the CHANGELOG with all the changes from this PR and the previous #248. Co-authored-by: Cliff L. Biffle <[email protected]> Co-authored-by: Peter Taylor <[email protected]> Co-authored-by: Hugues de Valon <[email protected]> Co-authored-by: Jonas Schievink <[email protected]> Co-authored-by: Adam Greig <[email protected]>
CC #236
Signed-off-by: Daniel Egger [email protected]