done, and also commit:
d4983d155f3172344dd55196b3918fc14b1c5d8b... abi: event: add
ODP_EVENT_IPSEC_STATUS
removed.
Maxim.
On 06/02/17 21:53, Bill Fischofer wrote:
> Maxim, should commit 033cd2a5c7c7dbc325d792c8e91389af7aa2eef0 be part
> of this release?
>
> abi: event: add
On 06/02/17 21:53, Bill Fischofer wrote:
> Maxim, should commit 033cd2a5c7c7dbc325d792c8e91389af7aa2eef0 be part
> of this release?
>
No, thanks for review, will remove it now.
Maxim.
> abi: event: add ODP_EVENT_IPSEC_RESULT
>
> Update ABI spec with the new IPSEC event type.
>
>
Maxim, should commit 033cd2a5c7c7dbc325d792c8e91389af7aa2eef0 be part
of this release?
abi: event: add ODP_EVENT_IPSEC_RESULT
Update ABI spec with the new IPSEC event type.
Signed-off-by: Petri Savolainen
Signed-off-by: Dmitry Eremin-Solenikov
On Fri, Jun 2, 2017 at 1:34 PM, Maxim Uvarov wrote:
> everything is prepared and only changelog and tagging is needed.
>
> Bill can you take care about that? I tested this branch on my
> github/travis and it was ok. Results for main repo have to be updated by
> travis in
As I mentioned yesterday:
* ipsec.h is still in next branch, but should be removed from there. IPsec API
should not be released yet.
* Crypto rework ([PATCH API-NEXT v5 00/23] Major cryptography code rework)
should be merged into api-next and from there to next branch, since it fixes
many
After quick comparison between next and api-next: ipsec.h should not yet be in
next branch == not in next release.
Also, it would be good to have these in next release
* checkpatch/spelling (master)
* crypto bug fixes/missing implementation series (api-next)
-Petri
From: Maxim Uvarov
Ok, thanks for details. I will try to prepare release according to your
list on this week.
On 24 May 2017 at 10:38, Savolainen, Petri (Nokia - FI/Espoo) <
petri.savolai...@nokia.com> wrote:
> Hi,
>
> It's already two months since 1.14 release. We have again missed the
> target of a release per
Hi,
It's already two months since 1.14 release. We have again missed the target of
a release per month. Additionally, we have bunch of stuff in api-next that
could move to master, and thus to the next release.
From api-next these API spec files (or parts) are OK to move into master:
* entire