[dpdk-dev] RFC: DPDK Long Term Support

Mcnamara, John john.mcnamara at intel.com
Tue Jun 7 14:53:02 CEST 2016

> -----Original Message-----
> From: Matthew Hall [mailto:mhall at mhcomputing.net]
> Sent: Friday, June 3, 2016 7:17 PM
> To: Mcnamara, John <john.mcnamara at intel.com>
> Cc: dev <dev at dpdk.org>; Christian Ehrhardt
> <christian.ehrhardt at canonical.com>; Markos Chandras <mchandras at suse.de>;
> Panu Matilainen <pmatilai at redhat.com>
> Subject: Re: [dpdk-dev] RFC: DPDK Long Term Support
> >
> > What changes should not be backported
> > -------------------------------------
> >
> > * API or ABI breaking changes.
> I think this part needs some adjusting.
> It seems like there should be allowance for bug fixes where the original
> does break ABI but it is possible to make a version that doesn't.
> A lot of DPDK bug fixes I see would fall into this category and it isn't
> discussed.

Hi Matthew,

Agreed, we should allow fix to be backported even if the patch itself cannot be, for ABI reasons.


More information about the dev mailing list