[ao] fixing public v private for fuser_method_mappings.py

[HDCharles]

Stack from ghstack (oldest at bottom):

• [ao] fixing public v private for fx.backend_config_utils.py #86037
• [ao] fixing public v private for fx.quantization_types #86036
• [ao] fixing public v private for quantization_patterns.py #86034
• [ao] fixing public v private for fx.pattern_utils.py #86033
• [ao] fixing public v private for fx.graph_module.py #86032
• [ao] fixing public v private for quantization_types #86031
• [ao] fixing public v private for backend_config.native.py #86030
• -> [ao] fixing public v private for fuser_method_mappings.py #86029
• [ao] fixing public v private for fuse_modules.py #86028
• [ao] fixing public v private for torch/ao/quantization #86027

Summary: no significant changes, just added all

Test Plan: python test/test_public_bindings.py

Reviewers:

Subscribers:

Tasks:

Tags:

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit our office hours

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

✅ No Failures

As of commit 6522406:
💚 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]

/easycla

As part of the transition to the PyTorch Foundation, this project now requires contributions be covered under the new CLA. See #85559 for additional details.

This comment will trigger a new check of this PR. If you are already covered, you will simply see a new "EasyCLA" check that passes. If you are not covered, a bot will leave a new comment with a link to sign.

[HDCharles]

@pytorchmergebot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[pytorchmergebot]

Merge failed

Reason: Command git -C /home/runner/work/pytorch/pytorch cherry-pick -x 5ffaf8cbd7a8850f275e8e20603786ab8d674afa returned non-zero exit code 1

Auto-merging test/allowlist_for_publicAPI.json
CONFLICT (content): Merge conflict in test/allowlist_for_publicAPI.json
error: could not apply 5ffaf8cbd7... [ao] fixing public v private for fuser_method_mappings.py
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

Details for Dev Infra team

Raised by workflow job

[HDCharles]

@pytorchmergebot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[github-actions]

Hey @HDCharles.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.