Skip to content

8373231: ECDSAOperations::toAffinePoint is redundant#28691

Closed
johnshajiang wants to merge 1 commit intoopenjdk:masterfrom
johnshajiang:JDK-8373231
Closed

8373231: ECDSAOperations::toAffinePoint is redundant#28691
johnshajiang wants to merge 1 commit intoopenjdk:masterfrom
johnshajiang:JDK-8373231

Conversation

@johnshajiang
Copy link
Member

@johnshajiang johnshajiang commented Dec 8, 2025

ECDSAOperations::toAffinePoint should be removed, and AffinePoint::fromECPoint should be used instead.


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-8373231: ECDSAOperations::toAffinePoint is redundant (Bug - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28691

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Dec 8, 2025

👋 Welcome back jjiang! 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
Copy link

openjdk bot commented Dec 8, 2025

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

8373231: ECDSAOperations::toAffinePoint is redundant

Reviewed-by: mullan

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 327 new commits pushed to the master branch:

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 openjdk bot added the security security-dev@openjdk.org label Dec 8, 2025
@openjdk
Copy link

openjdk bot commented Dec 8, 2025

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

  • security

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.

@openjdk openjdk bot added the rfr Pull request is ready for review label Dec 8, 2025
@mlbridge
Copy link

mlbridge bot commented Dec 8, 2025

Webrevs

Copy link
Member

@myankelev myankelev left a comment

Choose a reason for hiding this comment

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

Correct me if I'm wrong, this seems to be changing public API, shouldn't it have a csr then?

Copy link
Member

Choose a reason for hiding this comment

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

Could you please update the bug id?

@seanjmullan
Copy link
Member

Correct me if I'm wrong, this seems to be changing public API, shouldn't it have a csr then?

It's a class in an internal package (sun.security.ec), so should not need a CSR.

/*
* @test
* @bug 8189189 8147502 8295010
* @bug 8189189 8147502 8295010 8373231
Copy link
Member

Choose a reason for hiding this comment

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

You are not testing something new here, so you should not add the bugid.

Copy link
Member Author

Choose a reason for hiding this comment

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

Just withdrew the last commit.

@openjdk
Copy link

openjdk bot commented Jan 9, 2026

@johnshajiang Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jan 9, 2026
@johnshajiang
Copy link
Member Author

/integrate

@openjdk
Copy link

openjdk bot commented Jan 10, 2026

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

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jan 10, 2026
@openjdk openjdk bot closed this Jan 10, 2026
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Jan 10, 2026
@openjdk
Copy link

openjdk bot commented Jan 10, 2026

@johnshajiang Pushed as commit a726e83.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integrated Pull request has been integrated security security-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

3 participants