I was thinking again about GMAC auth case. Currently GMAC just reuses cipher IV data fields, which is not future proof and not quite obvious. So let's add separate set of IV-related fields for authentication algorithms.
----------------github------------------------ /** Email created from pull request 352 (lumag:crypto_gmac_iv) ** https://github.com/Linaro/odp/pull/352 ** Patch: https://github.com/Linaro/odp/pull/352.patch ** Base sha: 177eeff39e19289e771119cfdffc515cb16f9db5 ** Merge commit sha: ea71bf34033ee74ce7f090f0212b9285ca13b1fe **/ ----------------/github------------------------ ----------------checkpatch.pl------------------------ total: 0 errors, 0 warnings, 0 checks, 71 lines checked to_send-p-000.patch has no obvious style problems and is ready for submission. total: 0 errors, 0 warnings, 0 checks, 36 lines checked to_send-p-001.patch has no obvious style problems and is ready for submission. total: 0 errors, 0 warnings, 0 checks, 55 lines checked to_send-p-002.patch has no obvious style problems and is ready for submission. total: 0 errors, 0 warnings, 0 checks, 120 lines checked to_send-p-003.patch has no obvious style problems and is ready for submission. ----------------/checkpatch.pl------------------------
