Skip to content

Conversation

pytorchbot
Copy link
Collaborator

This PR was created by the merge bot to help merge the original PR into the main branch.
ghstack PR number: #14380 by @digantdesai
^ Please use this as the source of truth for the PR details, comments, and reviews
ghstack PR base: https://github.com/pytorch/executorch/tree/gh/digantdesai/49/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/digantdesai/49/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/main
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/digantdesai/49/orig
@diff-train-skip-merge

…ock oss PRs

Pull Request resolved: #14380

As title
ghstack-source-id: 310388788
@exported-using-ghexport

Differential Revision: [D82651207](https://our.internmc.facebook.com/intern/diff/D82651207/)
Copy link

pytorch-bot bot commented Sep 17, 2025

🔗 Helpful Links

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

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 Sep 17, 2025
Copy link

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@lucylq lucylq merged commit 4872141 into main Sep 17, 2025
121 of 125 checks passed
@lucylq lucylq deleted the gh/digantdesai/49/orig branch September 17, 2025 22:50
@zingo
Copy link
Collaborator

zingo commented Sep 18, 2025

@digantdesai Do we want this on 1.0 branch also?

@digantdesai
Copy link
Contributor

Sure we can, it shouldn't make a big difference in OSS or 1.0.

@mergennachin
Copy link
Contributor

No need for 1.0

StrycekSimon pushed a commit to nxp-upstream/executorch that referenced this pull request Sep 23, 2025
…ock oss PRs (pytorch#14395)

This PR was created by the merge bot to help merge the original PR into
the main branch.
ghstack PR number: pytorch#14380 by
@digantdesai
^ Please use this as the source of truth for the PR details, comments,
and reviews
ghstack PR base:
https://github.com/pytorch/executorch/tree/gh/digantdesai/49/base
ghstack PR head:
https://github.com/pytorch/executorch/tree/gh/digantdesai/49/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/main
Merge bot PR head:
https://github.com/pytorch/executorch/tree/gh/digantdesai/49/orig
@diff-train-skip-merge

Co-authored-by: Digant Desai <digantdesai@meta.com>
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants