On Mon, Feb 05, 2018 at 10:34:00AM +0000, Ferruh Yigit wrote: > On 2/4/2018 3:33 PM, Pavan Nikhilesh wrote: > > Register octeontx-fpavf as platform HW mempool when net/octeontx pmd is > > used. > > > > Signed-off-by: Pavan Nikhilesh <pbhagavat...@caviumnetworks.com> > > --- > > > > v2 Changes: > > - fixed compilation issues caused by using experimental API in both meson > > and > > make. > > > > drivers/net/octeontx/Makefile | 2 ++ > > drivers/net/octeontx/meson.build | 2 ++ > > Meson patches are still going through the Bruce's tree. Can you please make > this > two separate patches (not patchset), I can get the driver one and Makefile, > Bruce can get meson one. > Hi Ferruh,
I disagree with this. Since the meson build is now merged into mainline, many patches will have meson file changes to keep things building. These patches should not go in the next-build tree but should be part of the tree the rest of the patch targets. It should not be permitted to apply a patch to next-net which breaks the meson build. Only patches which add new capabilities or drivers to the build system will go in my tree. Regards, /Bruce
