MPS: add linespace op

[kulinseth]

Fixes #ISSUE_NUMBER

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/78570
• 📄  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

✅ 1 Base Failures

As of commit 4489ef3 (more details on the Dr. CI page):

Expand to see more

---

✅ None of the CI failures appear to be your fault 💚

---

• 1/1 broken upstream at merge base 96c1348 on May 31 from 1:36pm to 4:14pm

---

🚧 1 fixed upstream failure:

These were probably caused by upstream breakages that were already fixed.

Please rebase on the viable/strict branch (expand for instructions)

If your commit is older than viable/strict, run these commands:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD

• pull / pytorch-xla-linux-bionic-py3.7-clang8 / test (xla, 1, 1, linux.2xlarge) on May 31 from 1:36pm to 4:14pm (96c1348 - d71816a)
  • 🔁 rerun

---

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

[kulinseth]

@pytorchbot merge this please

[pytorchmergebot]

Merge failed due to Refusing to merge as mandatory check(s) Lint, linux-docs / build-docs (cpp), linux-docs / build-docs (python), win-vs2019-cpu-py3 / build, win-vs2019-cuda11.3-py3 / build, linux-xenial-py3.7-gcc7-no-ops / build, linux-bionic-py3.7-clang9 / build, linux-xenial-py3.7-clang7-onnx / build, linux-xenial-py3.7-gcc7 / build, linux-xenial-py3.7-clang7-asan / build, linux-vulkan-bionic-py3.7-clang9 / build, linux-xenial-cuda11.3-py3.7-gcc7 / build, linux-bionic-cuda11.3-py3.7-clang9 / build, linux-xenial-py3-clang5-mobile-build / build, linux-xenial-py3-clang5-mobile-custom-build-static / build, pytorch-xla-linux-bionic-py3.7-clang8 / build, deploy-linux-xenial-cuda11.3-py3.7-gcc7 / build are pending/not yet run for rule superuser
Raised by https://github.com/pytorch/pytorch/actions/runs/2419306306

[malfet]

@pytorchbot merge this

[github-actions]

Hey @kulinseth.
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.