Fix type checking errors in fx/utils.py

[EshikaShah]

• Fix the Pyre type checking errors in torch/quantization/fx/utils.py

torch/quantization/fx/utils.py:490:4 Incompatible variable type [9]: target_module_type is declared to have type `Type[nn.modules.module.Module]` but is used as type `None`.

Fixes the issue: MLH-Fellowship/pyre-check/issues/75

[pytorch-probot]

CI Flow Status

⚛️ CI Flow

Ruleset - Version: v1
Ruleset - File: https://github.com/EshikaShah/pytorch/blob/1110741dca63d3875b5d58de64ace4c528bb2c80/.github/generated-ciflow-ruleset.json
PR ciflow labels: ciflow/default

Workflows	Labels (bold enabled)	Status
Triggered Workflows
linux-bionic-py3.6-clang9	ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/noarch, ciflow/xla	✅ triggered
linux-vulkan-bionic-py3.6-clang9	ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/vulkan	✅ triggered
linux-xenial-cuda11.3-py3.6-gcc7	ciflow/all, ciflow/cuda, ciflow/default, ciflow/linux	✅ triggered
linux-xenial-py3.6-clang7-asan	ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/sanitizers	✅ triggered
linux-xenial-py3.6-clang7-onnx	ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/onnx	✅ triggered
linux-xenial-py3.6-gcc5.4	ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux	✅ triggered
linux-xenial-py3.6-gcc7-bazel-test	ciflow/all, ciflow/bazel, ciflow/cpu, ciflow/default, ciflow/linux	✅ triggered
win-vs2019-cpu-py3	ciflow/all, ciflow/cpu, ciflow/default, ciflow/win	✅ triggered
win-vs2019-cuda11.3-py3	ciflow/all, ciflow/cuda, ciflow/default, ciflow/win	✅ triggered
Skipped Workflows
libtorch-linux-xenial-cuda10.2-py3.6-gcc7	ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux	🚫 skipped
libtorch-linux-xenial-cuda11.3-py3.6-gcc7	ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux	🚫 skipped
linux-bionic-cuda10.2-py3.9-gcc7	ciflow/all, ciflow/cuda, ciflow/linux, ciflow/slow	🚫 skipped
linux-xenial-cuda10.2-py3.6-gcc7	ciflow/all, ciflow/cuda, ciflow/linux, ciflow/slow	🚫 skipped
parallelnative-linux-xenial-py3.6-gcc5.4	ciflow/all, ciflow/cpu, ciflow/linux	🚫 skipped
periodic-libtorch-linux-xenial-cuda11.1-py3.6-gcc7	ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux, ciflow/scheduled	🚫 skipped
periodic-linux-xenial-cuda10.2-py3-gcc7-slow-gradcheck	ciflow/all, ciflow/cuda, ciflow/linux, ciflow/scheduled, ciflow/slow, ciflow/slow-gradcheck	🚫 skipped
periodic-linux-xenial-cuda11.1-py3.6-gcc7	ciflow/all, ciflow/cuda, ciflow/linux, ciflow/scheduled	🚫 skipped
periodic-win-vs2019-cuda11.1-py3	ciflow/all, ciflow/cuda, ciflow/scheduled, ciflow/win	🚫 skipped
puretorch-linux-xenial-py3.6-gcc5.4	ciflow/all, ciflow/cpu, ciflow/linux	🚫 skipped

You can add a comment to the PR and tag @pytorchbot with the following commands:

# ciflow rerun, "ciflow/default" will always be added automatically
@pytorchbot ciflow rerun

# ciflow rerun with additional labels "-l <ciflow/label_name>", which is equivalent to adding these labels manually and trigger the rerun
@pytorchbot ciflow rerun -l ciflow/scheduled -l ciflow/slow

For more information, please take a look at the CI Flow Wiki.

[facebook-github-bot]

Hi @EshikaShah!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/66311
• 📄  Preview docs built from this PR
• 📄  Preview C++ docs built from this PR
• 🔧  Opt-in to CIFlow to control what jobs run on your PRs

💊 CI failures summary and remediations

As of commit 5001f53 (more details on the Dr. CI page):

---

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

---

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

Follow this link to opt-out of these comments for your Pull Requests.

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

Click here to manually regenerate this comment.

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[facebook-github-bot]

@0xedward has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[0xedward]

Thanks for the PR @EshikaShah! I've imported it for internal review :)