Miscellaneous pre-release fixes #883
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MabezDev
requested changes
Oct 31, 2023
|
Ahh yeah thanks, this was previously brought to my attention but nobody opened an issue for that so it got forgotten. Will get that fixed shortly. |
katyo
pushed a commit
to katyo/esp-hal
that referenced
this pull request
Nov 6, 2023
* Temporarily disable async `SYSTIMER` implementation, remove mention from `CHANGELOG.md` * Remove a couple files which are not required * Fix warning for `sha` examples * Fix warning for non-C3 devices * s/interrupt_clear/clear_interrupt/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
embedded_hal_async::delay::DelayMsimplementationesp-wifiasynchmodule via a#[cfg()], rather than removing the implementation altogether, as it is a valid implementation.shaexamplesSYSTIMER'sinterrupt_clearfunction toclear_interruptI think this should put us in decent shape for our next round of releases. @MabezDev @bjoernQ lemme know if you can think of anything I'm forgetting, please.