Skip to content

[xnn update prep] Update ET Pthreadpool third-party to google #11507

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

Merged
merged 20 commits into from
Jun 26, 2025

Conversation

mcr229
Copy link
Contributor

@mcr229 mcr229 commented Jun 9, 2025

No description provided.

mcr229 added 3 commits June 9, 2025 15:10
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
@mcr229
Copy link
Contributor Author

mcr229 commented Jun 9, 2025

@mcr229 mcr229 requested a review from digantdesai as a code owner June 9, 2025 22:10
Copy link

pytorch-bot bot commented Jun 9, 2025

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

⏳ No Failures, 6 Pending

As of commit 7a0d6fb with merge base 32d2dfa (image):
💚 Looks good so far! There are no failures yet. 💚

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

@facebook-github-bot facebook-github-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 Jun 9, 2025
mcr229 added a commit that referenced this pull request Jun 9, 2025
ghstack-source-id: 0d2a023
ghstack-comment-id: 2957149457
Pull Request resolved: #11507
@mcr229 mcr229 changed the title Update ET Pthreadpool third-party to google [xnn update prep] Update ET Pthreadpool third-party to google Jun 9, 2025
@mcr229 mcr229 added the release notes: none Do not include this in the release notes label Jun 9, 2025
Copy link
Contributor

@digantdesai digantdesai left a comment

Choose a reason for hiding this comment

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

I guess a drop in replacement?

mcr229 added 2 commits June 11, 2025 14:44
[ghstack-poisoned]
[ghstack-poisoned]
mcr229 added a commit that referenced this pull request Jun 11, 2025
ghstack-source-id: f0eec73
ghstack-comment-id: 2957149457
Pull Request resolved: #11507
mcr229 added 2 commits June 13, 2025 13:22
[ghstack-poisoned]
[ghstack-poisoned]
mcr229 added a commit that referenced this pull request Jun 13, 2025
ghstack-source-id: d089ac9
ghstack-comment-id: 2957149457
Pull Request resolved: #11507
mcr229 added 2 commits June 23, 2025 10:27
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
mcr229 added a commit that referenced this pull request Jun 24, 2025
ghstack-source-id: 87773e7
ghstack-comment-id: 2957149457
Pull Request resolved: #11507
kedarnath03 pushed a commit to kedarnath03/executorch that referenced this pull request Jun 25, 2025
ghstack-source-id: 6f6ebb8
ghstack-comment-id: 2957149457
Pull Request resolved: pytorch/executorch#11507
mcr229 added 2 commits June 25, 2025 13:30
[ghstack-poisoned]
[ghstack-poisoned]
mcr229 added a commit to mcr229/executorch that referenced this pull request Jun 25, 2025
ghstack-source-id: 76b550b
ghstack-comment-id: 2957149457
Pull Request resolved: pytorch#11507
mcr229 and others added 7 commits June 26, 2025 10:08
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
Base automatically changed from gh/mcr229/29/head to main June 26, 2025 20:30
@mcr229 mcr229 merged commit 74aeade into main Jun 26, 2025
196 checks passed
@mcr229 mcr229 deleted the gh/mcr229/30/head branch June 26, 2025 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk 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.

4 participants