[dpdk-ci] Master compilation failures in Intel CI
Thomas Monjalon
thomas at monjalon.net
Tue Jan 14 09:04:06 CET 2020
14/01/2020 08:18, Chen, Zhaoyan:
> - most of the patches in patchset are aimed to specific PMD driver,
> but just several patches for makefile/build script/config file(common files).. in patchset.
> (e.g. https://patchwork.dpdk.org/patch/64384/)
> This kind of patchset will be pointed to dpdk master
We should filter out config/, mk/ and MAINTAINERS in the decision.
> - one patchset includes document change and other specific PMD driver change.
> This kind of patchset will be pointed to dpdk master
For doc/, we must make sure each part of the doc is well sorted
in MAINTAINERS so we can distinguish crypto and ethdev docs for instance.
> For these 2 situations, basically, next-* branches are ahead of master,
> developers expected their patches could be tested on next-*, since that is code base under developing.
>
> So applying these kinds of patchsets to next-* are more meaningful for them.
I agree.
More information about the ci
mailing list