-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
JDK-8260625: Rename MetaspaceExpand_lock #2308
JDK-8260625: Rename MetaspaceExpand_lock #2308
Conversation
👋 Welcome back stuefe! A progress list of the required criteria for merging this PR into |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me.
@tstuefe 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:
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 10 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
Thanks! Trivial too? |
I don't see why not. The patch is trivial in substance, but I would like to see builds to complete first. |
Oh for sure. |
/integrate |
@tstuefe Since your change was applied there have been 16 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit b7b391b. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
* Copyright (c) 2020, Oracle and/or its affiliates. All rights reserved. | ||
* Copyright (c) 2020 SAP SE. All rights reserved. | ||
* Copyright (c) 2020, 2021, Oracle and/or its affiliates. All rights reserved. | ||
* Copyright (c) 2020, 2021 SAP SE. All rights reserved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There should add a ',' after 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, Yumin! Sorry, I already had integrated under the trivial rule. And yes, Coleen is right, we do not have that trailing comma (don't ask me why).
..Thomas
Mailing list message from Coleen Phillimore on hotspot-runtime-dev: On 1/29/21 2:00 PM, Yumin Qi wrote:
Turns out that the SAP copyright doesn't have the trailing comma. Now |
Mailing list message from Yumin Qi on hotspot-runtime-dev: Thanks, now I know:) Yumin On 1/29/21 11:19 AM, Coleen Phillimore wrote:
|
Hi, may I have reviews please for this trivial change:
MetaspaceExpand_lock is a potentially confusing misnomer for the casual code reader, since it does not only guard metaspace expansion but guards access to all central metaspace structures for expansion, reclamation, access to freelist etc.
With this patch it is renamed to the more generic "Metaspace_lock".
Thanks, Thomas
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2308/head:pull/2308
$ git checkout pull/2308