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

Update current support #381

Merged
merged 2 commits into from
Dec 11, 2023
Merged

Update current support #381

merged 2 commits into from
Dec 11, 2023

Conversation

SergioGasquez
Copy link
Member

No description provided.

@SergioGasquez
Copy link
Member Author

Not sure if the MSRV is up to date, maybe we could include a MSRV CI check?

Copy link
Contributor

@bjoernQ bjoernQ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - Thanks!

@bjoernQ bjoernQ merged commit 5f32459 into esp-rs:main Dec 11, 2023
8 checks passed
@@ -62,7 +63,7 @@ Within this crate, `CCOMPARE0` CPU timer is used for timing, ensure that in your

When using USB-SERIAL-JTAG (for example by selecting `jtag-serial` in [`esp-println`](https://crates.io/crates/esp-println)) you have to activate the feature `phy-enable-usb`.

Don't use this feature if your are _not_ using USB-SERIAL-JTAG as it might reduce WiFi performance.
Don't use this feature if you are _not__ using USB-SERIAL-JTAG as it might reduce WiFi performance.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this new underscore breaks the markdown rendering.

Suggested change
Don't use this feature if you are _not__ using USB-SERIAL-JTAG as it might reduce WiFi performance.
Don't use this feature if you are _not_ using USB-SERIAL-JTAG as it might reduce WiFi performance.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ups, good catch, just opened #382 to fix it, for some reason the "Fix" VS Code applied with the Grammarly extension changed it, not sure why.

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

Successfully merging this pull request may close these issues.

3 participants