Skip to content

Conversation

@GregoryComer
Copy link
Member

@GregoryComer GregoryComer commented Oct 22, 2025

Summary

Bulk pick doc updates using https://github.com/pytorch/executorch/blob/main/scripts/pick_doc_commits.py.

I also manually included eb05056, which has some example changes, since it's a doc update PR.

I sanity checked this by running git diff HEAD upstream/main -- docs/source and the diff didn't show any surprises. There were some changes on main related to larger PRs that haven't been picked (NXP visualizer, for example), but everything else is in sync.

roman-janik-nxp and others added 24 commits October 21, 2025 17:18
This PR updates NXP backend Readmes in backend and examples directories.

-

cc @robert-kalmar @JakeStevens @digantdesai
Updated link to Core ATen operator set documentation.

### Summary
[PLEASE REMOVE] See [CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests)
for ExecuTorch PR guidelines.

[PLEASE REMOVE] If this PR closes an issue, please add a `Fixes
#<issue-id>` line.

[PLEASE REMOVE] If this PR introduces a fix or feature that should be
the upcoming release notes, please add a "Release notes: <area>" label.
For a list of available release notes labels, check out
[CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests).

### Test plan
[PLEASE REMOVE] How did you test this PR? Please write down any manual
commands you used and note down tests that you have written if
applicable.
Summary:
Title says it all!

Add docs for the Samsung backend based on the template introduced in
pytorch#14873.
### Summary
Add Pico2 Tutorials on Raspberry Pi 

[PLEASE REMOVE] See [CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests)
for ExecuTorch PR guidelines.

[PLEASE REMOVE] If this PR closes an issue, please add a `Fixes
#<issue-id>` line.

[PLEASE REMOVE] If this PR introduces a fix or feature that should be
the upcoming release notes, please add a "Release notes: <area>" label.
For a list of available release notes labels, check out
[CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests).

### Test plan
[PLEASE REMOVE] How did you test this PR? Please write down any manual
commands you used and note down tests that you have written if
applicable.
1. Make Android doc more Dev focused / friendly
(Quick Start Navigation , More Clear Pathfinding & Logical Flow for
Devs)
3. Update links to be relevant in Android  sections
4. Fix the broken vulkan & coreML links from Android & iOS flow
5. Fix navigation related issues

[PLEASE REMOVE] See [CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests)
for ExecuTorch PR guidelines.

[PLEASE REMOVE] If this PR closes an issue, please add a `Fixes

[PLEASE REMOVE] If this PR introduces a fix or feature that should be
the upcoming release notes, please add a "Release notes: <area>" label.
For a list of available release notes labels, check out
[CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests).

[PLEASE REMOVE] How did you test this PR? Please write down any manual
commands you used and note down tests that you have written if
applicable.
…torch#15266)

### Summary
[PLEASE REMOVE] See [CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests)
for ExecuTorch PR guidelines.

[PLEASE REMOVE] If this PR closes an issue, please add a `Fixes
#<issue-id>` line.

[PLEASE REMOVE] If this PR introduces a fix or feature that should be
the upcoming release notes, please add a "Release notes: <area>" label.
For a list of available release notes labels, check out
[CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests).

### Test plan
[PLEASE REMOVE] How did you test this PR? Please write down any manual
commands you used and note down tests that you have written if
applicable.
…h#15287)

[PLEASE REMOVE] See [CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests)
for ExecuTorch PR guidelines.

[PLEASE REMOVE] If this PR closes an issue, please add a `Fixes

[PLEASE REMOVE] If this PR introduces a fix or feature that should be
the upcoming release notes, please add a "Release notes: <area>" label.
For a list of available release notes labels, check out
[CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests).

[PLEASE REMOVE] How did you test this PR? Please write down any manual
commands you used and note down tests that you have written if
applicable.
This PR updates the Voxtral README to document Metal backend support on
Apple Silicon.
Update unsloth QAT story to use qwen example, which has more details
than llama example.
### Summary

Update Getting Started and Build from Source Docs:
* Integrate Windows steps into the main flow with minor Windows-specific
callouts.
* Clarify top-level flow for building from source - add a table by use
case.
 * Clarify building ET as a submodule vs standalone build.
* Re-order, re-word, and clean up the content related to building from
source.
 * Add info on NDK build for Android.

Tracked in pytorch#14791 and
pytorch#14759.

cc @mergennachin @byjlw
Prototype an updated doc structure for the XNNPACK backend. Extract a
common template out under docs/source/backends/tempate/

This PR updates the doc structure as follows. Under the template, the
landing page is required, partitioner, quantization, and op support docs
are recommended, and the rest are optional.

- XNNPACK Backend
   - Quantization (recommended)
   - Partitioner APIs (recommended)
   - Operator Support (optional)
   - Architecture and Internals (optional)
   - Tutorials (optional)
   - Guides (optional)
### Summary
[PLEASE REMOVE] See [CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests)
for ExecuTorch PR guidelines.

[PLEASE REMOVE] If this PR closes an issue, please add a `Fixes
#<issue-id>` line.

[PLEASE REMOVE] If this PR introduces a fix or feature that should be
the upcoming release notes, please add a "Release notes: <area>" label.
For a list of available release notes labels, check out
[CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests).

### Test plan
[PLEASE REMOVE] How did you test this PR? Please write down any manual
commands you used and note down tests that you have written if
applicable.
@GregoryComer GregoryComer requested a review from cccclai as a code owner October 22, 2025 00:53
@pytorch-bot
Copy link

pytorch-bot bot commented Oct 22, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/15338

Note: Links to docs will display an error until the docs builds have been completed.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 22, 2025
@GregoryComer GregoryComer added the release notes: none Do not include this in the release notes label Oct 22, 2025
@psiddh psiddh self-requested a review October 22, 2025 00:58
Copy link
Contributor

@psiddh psiddh left a comment

Choose a reason for hiding this comment

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

Lets Go!

zonglinpeng and others added 2 commits October 21, 2025 18:04
Summary: ~

Differential Revision: D85064213
### Summary
Fix heading level for build verification, cleanup wording on Windows
reqs, update android presets since they were split by arch.
@GregoryComer GregoryComer merged commit 72d7ba8 into pytorch:release/1.0 Oct 22, 2025
119 of 124 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. release notes: none Do not include this in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.