Update BN_add.pod documentation so they are consistent with their header declarations. Fixes issue #19521

[JulieDzeze1]

Update BN_add.pod documentation so they are consistent with their header declarations. Fixes issue #19521 on OpenSSL's master branch.

[JulieDzeze1]

I created a PR to meet the requirements for the SWE assignment for CSEC 659. @bbbrumley please review when you get the chance. Thank you!

[bbbrumley]

Looks good to me :) Thank you, @JulieDzeze1

[romen]

LGTM: it looks like these consts predate even 1.1.1 in the headers!

Thanks for your contribution @JulieDzeze1

[romen]

Sorry @JulieDzeze1 I was too hasty in my review: we would need you to rebase your commit on top of latest master, as we do not allow Merge commits.

Can you handle this or do you need furhter guidance?

[romen]

I agree with CLA: trivial

[romen]

This would fix #19521 but for some reason the GitHub UI does not let me link the issue with this PR or viceversa.

[JulieDzeze1]

Sorry @JulieDzeze1 I was too hasty in my review: we would need you to rebase your commit on top of latest master, as we do not allow Merge commits.

Can you handle this or do you need furhter guidance?

Hi, I've attempted to rebase my commit but this is a little complicated since this is a forked repository from the main project. How should I approach it?

[t8m]

Hi, I've attempted to rebase my commit but this is a little complicated since this is a forked repository from the main project. How should I approach it?

You do not even need to rebase against fresh master branch. Just remove the merge commit with git reset --hard HEAD~ ; git push --force.