8000 fix linalg inv doc by simonJJJ · Pull Request #77079 · pytorch/pytorch · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix linalg inv doc #77079

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

Closed
wants to merge 1 commit into from
Closed

fix linalg inv doc #77079

wants to merge 1 commit into from

Conversation

simonJJJ
Copy link
Contributor
@simonJJJ simonJJJ commented May 9, 2022

I believe it is a doc typo, so I fix it.

@facebook-github-bot
Copy link
Contributor
facebook-github-bot commented May 9, 2022

🔗 Helpful links

✅ No Failures (0 Pending)

As of commit 54cc36b (more details on the Dr. CI page):

Expand to see more

💚 💚 Looks good so far! There are no failures yet. 💚 💚


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.

Copy link
Collaborator
@lezcano lezcano left a comment

Choose a reason for hiding this comment

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

It is indeed, thank you for this.

@lezcano
Copy link
Collaborator
lezcano commented May 9, 2022

@pytorchmergebot merge this please

@pytorchmergebot
Copy link
Collaborator

Merge failed due to Refusing to merge as mandatory check(s) Lint are not yet run for rule Linear Algebra
Raised by https://github.com/pytorch/pytorch/actions/runs/2294981879

@lezcano
Copy link
Collaborator
lezcano commented May 9, 2022

@pytorchmergebot merge this please

@github-actions
Copy link
Contributor
github-actions bot commented May 9, 2022

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

facebook-github-bot pushed a commit that referenced this pull request May 13, 2022
Summary:
I believe it is a doc typo, so I fix it.

Pull Request resolved: #77079
Approved by: https://github.com/Lezcano

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/bcd2167bb5d977bf758835f2c7a8b8cc50ff3d29

Reviewed By: malfet

Differential Revision: D36250660

Pulled By: malfet

fbshipit-source-id: f1dc6fbf0ec58f2a5bd5bbc585b3b564d7f30477
@lezcano lezcano added the topic: docs topic category label Jun 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
0