[dpdk-dev] [PATCH v2 0/6] crypto/mvsam: add new features and fixes
Akhil Goyal
akhil.goyal at nxp.com
Wed Sep 26 12:51:16 CEST 2018
On 9/26/2018 3:33 PM, Andrzej Ostruszka wrote:
> 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?
If it is dependent on net-next, then I will defer this set to be applied
next week when the master is in sync with net-next.
>
>> 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.
No need for now.. I will wait for master to get in sync and then apply
the dependent patches.
Is there any series which can be applied without any dependency?
And it would be a good practice to mention the dependencies in the cover
note in future.
-Akhil
More information about the dev
mailing list