> -----Original Message----- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jay Rolette > Sent: Wednesday, April 6, 2016 1:41 PM > To: Yuanhan Liu <yuanhan.liu at linux.intel.com> > Cc: Arnon Warshavsky <arnon at qwilt.com>; Trahe, Fiona > <fiona.trahe at intel.com>; Thomas Monjalon <thomas.monjalon at 6wind.com>; > dev at dpdk.org > Subject: Re: [dpdk-dev] DPDK namespace > > On Wed, Apr 6, 2016 at 12:26 AM, Yuanhan Liu <yuanhan.liu at linux.intel.com> > wrote: > > This last point that yliu brings up is the one that worries me. DPDK > already has a serious problem with the patch backlog. It can take months > for even small bug fixes to get merged. > > From the app side, it's not the end of the world if there is a one time, > single shot change to the prefix. However, I'm not sure it's worth it > because of the impact on patches that have been submitted. As others have > mentioned, google can sort the rte_* references just fine.
Hi, Agreed on patches. And if we wanted to do a Long Term Support branch/release based on DPDK 2.2.0 or 16.04 then backporting fixes would be a pain. John. --