8276685: Malformed Javadoc inline tags in JDK source in /jdk/management/jfr/RecordingInfo.java

[egahlin]

Hi,

Could I have review of this Javadoc fix.

Thanks
Erik

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8276685: Malformed Javadoc inline tags in JDK source in /jdk/management/jfr/RecordingInfo.java

Reviewers

• Markus Grönlund (@mgronlun - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6573/head:pull/6573
$ git checkout pull/6573

Update a local copy of the PR:
$ git checkout pull/6573
$ git pull https://git.openjdk.java.net/jdk pull/6573/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 6573

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6573.diff

[bridgekeeper]

👋 Welcome back egahlin! 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]

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

• hotspot-jfr

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 (c4afe916)

[openjdk]

@egahlin 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:

8276685: Malformed Javadoc inline tags in JDK source in /jdk/management/jfr/RecordingInfo.java

Reviewed-by: mgronlun

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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.

[egahlin]

/integrate

[openjdk]

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

• 40fef23: 8275908: Record null_check traps for calls and array_check traps in the interpreter
• 3d810ad: 8277411: C2 fast_unlock intrinsic on AArch64 has unnecessary ownership check
• ce0234b: 8277860: PPC: Remove duplicate info != NULL check

Your commit was automatically rebased without conflicts.

[openjdk]

@egahlin Pushed as commit b9eb532.

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