From: Andrzej Ostruszka <amo@semihalf.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, dev@dpdk.org
Cc: mw@semihalf.com, nadavh@marvell.com
Subject: Re: [dpdk-dev] [PATCH v2 0/6] crypto/mvsam: add new features and fixes
Date: Wed, 26 Sep 2018 12:03:50 +0200 [thread overview]
Message-ID: <dd86c13e-51f9-2763-141a-097e7568f4ea@semihalf.com> (raw)
In-Reply-To: <6d84f9e7-bfb5-61e8-631a-2684ab03d6d5@nxp.com>
Hello Akhil
On 25.09.2018 17:24, Akhil Goyal wrote:
> Hi Andrzej,
[...]
> I am not able to cleanly apply your 3 patchsets.
> http://patches.dpdk.org/user/todo/dpdk/?series=1172
> http://patches.dpdk.org/user/todo/dpdk/?series=1440
> http://patches.dpdk.org/user/todo/dpdk/?series=1442
>
> Could you please rebase and send a single patchset if possible.
The problem is that next-crypto is not in sync with next-net. In
particular it is missing this commit:
7a39d1b common/mvep: add common code for Marvell drivers
Could you rebase/merge next-crypto with next-net to have this commit?
> Also, I believe http://patches.dpdk.org/patch/44254/
> can be squashed with http://patches.dpdk.org/patch/45104/
No problem I can package all patches into one set but as mentioned above
some of them depend on common mvep code introduced already in next-net.
Best regards
Andrzej
next prev parent reply other threads:[~2018-09-26 10:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 13:54 [dpdk-dev] [PATCH " Tomasz Duszynski
2018-08-24 13:54 ` [dpdk-dev] [PATCH 1/6] crypto/mvsam: fix shared library build Tomasz Duszynski
2018-09-17 14:00 ` Akhil Goyal
2018-08-24 13:54 ` [dpdk-dev] [PATCH 2/6] crypto/mvsam: update hash digest sizes Tomasz Duszynski
2018-09-17 13:54 ` Akhil Goyal
2018-08-24 13:54 ` [dpdk-dev] [PATCH 3/6] crypto/mvsam: add support for HMAC SHA224 Tomasz Duszynski
2018-09-17 13:57 ` Akhil Goyal
2018-09-21 14:49 ` Andrzej Ostruszka
2018-08-24 13:54 ` [dpdk-dev] [PATCH 4/6] crypto/mvsam: add support for AES ECB Tomasz Duszynski
2018-09-17 13:59 ` Akhil Goyal
2018-09-21 14:46 ` Andrzej Ostruszka
2018-08-24 13:54 ` [dpdk-dev] [PATCH 5/6] crypto/mvsam: add support for crypto/auth NULL algorithms Tomasz Duszynski
2018-08-24 13:54 ` [dpdk-dev] [PATCH 6/6] crypto/mvsam: add 3DES ECB to the capabilities list Tomasz Duszynski
2018-09-21 14:53 ` [dpdk-dev] [PATCH v2 0/6] crypto/mvsam: add new features and fixes Andrzej Ostruszka
2018-09-21 14:53 ` [dpdk-dev] [PATCH v2 1/6] crypto/mvsam: fix shared library build Andrzej Ostruszka
2018-09-21 14:53 ` [dpdk-dev] [PATCH v2 2/6] crypto/mvsam: update hash digest sizes Andrzej Ostruszka
2018-09-21 14:53 ` [dpdk-dev] [PATCH v2 3/6] crypto/mvsam: support for HMAC SHA224 Andrzej Ostruszka
2018-09-21 14:53 ` [dpdk-dev] [PATCH v2 4/6] crypto/mvsam: support for AES ECB Andrzej Ostruszka
2018-09-21 14:53 ` [dpdk-dev] [PATCH v2 5/6] crypto/mvsam: support for crypto/auth NULL algorithms Andrzej Ostruszka
2018-09-21 14:53 ` [dpdk-dev] [PATCH v2 6/6] crypto/mvsam: add 3DES ECB to the capabilities list Andrzej Ostruszka
2018-09-25 15:24 ` [dpdk-dev] [PATCH v2 0/6] crypto/mvsam: add new features and fixes Akhil Goyal
2018-09-26 10:03 ` Andrzej Ostruszka [this message]
2018-09-26 10:51 ` Akhil Goyal
2018-10-01 13:28 ` Akhil Goyal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd86c13e-51f9-2763-141a-097e7568f4ea@semihalf.com \
--to=amo@semihalf.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).