-
Notifications
You must be signed in to change notification settings - Fork 697
NXP backend: Fix missing NXP backend documentation page in release 1.0 documentation #14851
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/14851
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 Cancelled Jobs, 1 Unrelated FailureAs of commit 5eba1de with merge base e0dda90 ( CANCELLED JOBS - The following jobs were cancelled. Please retry:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
6e74e58 to
5eba1de
Compare
|
This can be considered a bugfix PR since NXP backend link was incorrect. |
|
@pytorchbot label "module: nxp" |
| - [Cadence](backends-cadence) | ||
| - [OpenVINO](build-run-openvino) | ||
| - [NXP](backend-nxp) | ||
| - [NXP](backends-nxp) |
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.
We just did a big refactoring (and will cherry-pick onto release/1.0 branch soon)
here's the preview:
https://docs.pytorch.org/executorch/main/
Please rebase to latest main and change appropriately.
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 was not sure if the new look of documentation is supposed to be a part of the release so I raised PRs to both main and release/1.0. I am closing this one since the PR to main was merged already.
Summary
Test plan
Documentation built locally using Makefile without any problems.
cc @robert-kalmar @JakeStevens @digantdesai