8360548: Parallel: Remove outdated comments in MutableNUMASpace::bias_region

[albertnetymk]

Trivial removing outdated comments.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8360548: Parallel: Remove outdated comments in MutableNUMASpace::bias_region (Enhancement - P4)

Reviewers

• Thomas Schatzl (@tschatzl - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25984/head:pull/25984
$ git checkout pull/25984

Update a local copy of the PR:
$ git checkout pull/25984
$ git pull https://git.openjdk.org/jdk.git pull/25984/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25984

View PR using the GUI difftool:
$ git pr show -t 25984

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25984.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back ayang! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@albertnetymk This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8360548: Parallel: Remove outdated comments in MutableNUMASpace::bias_region

Reviewed-by: tschatzl

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 7 new commits pushed to the master branch:

• 1ca008f: 8360255: runtime/jni/checked/TestLargeUTF8Length.java fails with -XX:-CompactStrings
• cf75f1f: 8358821: patch_verified_entry causes problems, use nmethod entry barriers instead
• 5252608: 8225354: serviceability/jvmti/ModuleAwareAgents/ThreadStart failed with Didn't get ThreadStart events in VM early start phase!
• ... and 4 more: https://git.openjdk.org/jdk/compare/52c6044fe48f2e964be4c4603a865143f0d43f90...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@albertnetymk The following label will be automatically applied to this pull request:

• hotspot-gc

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (b6702143)

[tschatzl]

Trivial.

[albertnetymk]

Thanks for review.

/integrate

[openjdk]

Going to push as commit 5a1301d.
Since your change was applied there have been 8 commits pushed to the master branch:

• 5039b42: 8359437: Make users and test suite not able to set LockingMode flag
• 1ca008f: 8360255: runtime/jni/checked/TestLargeUTF8Length.java fails with -XX:-CompactStrings
• cf75f1f: 8358821: patch_verified_entry causes problems, use nmethod entry barriers instead
• ... and 5 more: https://git.openjdk.org/jdk/compare/52c6044fe48f2e964be4c4603a865143f0d43f90...master

Your commit was automatically rebased without conflicts.

[openjdk]

@albertnetymk Pushed as commit 5a1301d.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.