[dpdk-dev] [PATCH 0/2] baseband: fix drivers API

Thomas Monjalon thomas at monjalon.net
Wed Oct 7 13:07:47 CEST 2020


07/10/2020 13:06, Thomas Monjalon:
> 07/10/2020 12:52, Maxime Coquelin:
> > On 10/7/20 12:29 PM, Thomas Monjalon wrote:
> > > 07/10/2020 12:12, Maxime Coquelin:
> > >> On 10/7/20 12:09 PM, Thomas Monjalon wrote:
> > >>> 07/10/2020 10:22, Maxime Coquelin:
> > >>>> On 10/6/20 9:42 PM, Akhil Goyal wrote:
> > >>>>>>
> > >>>>>> The series prefixes drivers APIs with rte_<drv_name>_ in
> > >>>>>> order to avoid namespace pollution.
> > >>>>>>
> > >>>>>> These APIs are experimental, so no need to follow the
> > >>>>>> deprecation process.
> > >>>>>>
> > >>>>> Added Fixes commit in patch description.
> > >>>>
> > >>>> Thanks for applying it to your tree.
> > >>>>
> > >>>> I did not add Fixes tag and Cc'ed stable at dpdk.org on purpose,
> > >>>> because I thought it is was not a good idea to backport API changes,
> > >>>> even if this is experimental it might be annoying for the user.
> > >>>>
> > >>>> Thomas, do you confirm?
> > >>>
> > >>> Absolutely: API must not change in a stable branch.
> > >>>
> > >>> If an API is changed, it must be in the release notes.
> > >>
> > >> Ok, even for experimental APIs? I thought not.
> > > 
> > > Yes, experimental means it can change in the main branch
> > > without prior notice. But it must be noted when it's changed.
> > 
> > Ok, do you want me to send add-on patches that you will squash when
> > pulling Akhil's branch?
> 
> Yes please

Better: Akhil can squash in his tree and remove the Cc: stable tag.





More information about the dev mailing list