Skip to content

[PATCH API-NEXT v1] support for SHA-1/-512#10

Closed
lumag wants to merge 4 commits intoOpenDataPlane:api-nextfrom
lumag:crypto-update
Closed

[PATCH API-NEXT v1] support for SHA-1/-512#10
lumag wants to merge 4 commits intoOpenDataPlane:api-nextfrom
lumag:crypto-update

Conversation

@lumag
Copy link
Copy Markdown

@lumag lumag commented Apr 3, 2017

  • major consolidation of cryptographic code
  • support for SHA-1/-512

@lumag lumag mentioned this pull request Apr 3, 2017
@lumag
Copy link
Copy Markdown
Author

lumag commented Apr 27, 2017

@muvarov could you please merge master into api-next, so that I can rebase this PR? Thank you in advance.

Dmitry Eremin-Solenikov added 4 commits May 2, 2017 23:31
Signed-off-by: Dmitry Eremin-Solenikov <dmitry.ereminsolenikov@linaro.org>
Signed-off-by: Dmitry Eremin-Solenikov <dmitry.ereminsolenikov@linaro.org>
Signed-off-by: Dmitry Eremin-Solenikov <dmitry.ereminsolenikov@linaro.org>
Signed-off-by: Dmitry Eremin-Solenikov <dmitry.ereminsolenikov@linaro.org>
@lumag lumag force-pushed the crypto-update branch from 1e10cfe to d3f7bbe Compare May 2, 2017 20:32
@muvarov muvarov changed the title crypto rework and support for SHA-1/-512 [PATCH API-NEXT v1] crypto rework and support for SHA-1/-512 May 2, 2017
@muvarov muvarov removed the Email_sent label May 2, 2017
@codecov-io
Copy link
Copy Markdown

codecov-io commented May 2, 2017

Codecov Report

❗ No coverage uploaded for pull request base (api-next@0b1dbf3). Click here to learn what that means.
The diff coverage is 88.57%.

Impacted file tree graph

@@             Coverage Diff             @@
##             api-next      #10   +/-   ##
===========================================
  Coverage            ?   78.85%           
===========================================
  Files               ?      188           
  Lines               ?    33262           
  Branches            ?        0           
===========================================
  Hits                ?    26228           
  Misses              ?     7034           
  Partials            ?        0
Impacted Files Coverage Δ
...n_plat/validation/api/crypto/odp_crypto_test_inp.c 84.67% <88.57%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0b1dbf3...d3f7bbe. Read the comment docs.

@lumag
Copy link
Copy Markdown
Author

lumag commented May 2, 2017

Now as major consolidation part was merged, this PR contains only SHA-1/SHA-512 implementation.

@lumag
Copy link
Copy Markdown
Author

lumag commented May 9, 2017

Needs to be updated after #24 is merged in.

@lumag lumag changed the title [PATCH API-NEXT v1] crypto rework and support for SHA-1/-512 [PATCH API-NEXT v1] support for SHA-1/-512 May 25, 2017
@lumag lumag closed this Jun 1, 2017
@lumag lumag deleted the crypto-update branch June 1, 2017 06:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants