On 12/22/2016 11:35 AM, Andrew Rybchenko wrote: > On 12/22/2016 02:04 PM, Ferruh Yigit wrote: >> On 12/21/2016 11:40 AM, Andrew Rybchenko wrote: >>> On 12/21/2016 02:37 PM, Neil Horman wrote: >>>> On Wed, Dec 21, 2016 at 12:21:14PM +0300, Andrew Rybchenko wrote: >>>>> On 12/20/2016 08:26 PM, Thomas Monjalon wrote: >>>>>>>> Add a new macro RTE_PMD_REGISTER_KMOD_DEP() that allows a driver to >>>>>>>> declare the list of kernel modules required to run properly. >>>>>>>> >>>>>>>> Today, most PCI drivers require uio/vfio. >>>>>>>> >>>>>>>> Signed-off-by: Olivier Matz <olivier.m...@6wind.com> >>>>>>>> Acked-by: Fiona Trahe <fiona.tr...@intel.com> >>>>>>> Acked-by: Adrien Mazarguil <adrien.mazarg...@6wind.com> >>>>>> Applied in main tree, thanks >>>>> Is there any plan on how it will be done/solved for a new drivers in >>>>> dpdk-next-net? >>>>> Should I care about it for sfc? >>>>> >>>> Given that all pmdinfo information is opt-in (that is to say not >>>> obligatory), >>>> you can now wait until net-next does its next rebase, and as you continue >>>> your >>>> development of the sfc driver, you can add the use of this macro in at your >>>> leisure. As more people do that, we will arrive at 100% coverage >>> I see. Will do. Thanks. >>> >> Hi Andrew, >> >> Patch rebased to next-net, would you mind doing the mentioned patch for it? > > Hi Ferruh, > > done. I was in doubts which changeset to specify in fixes, but finally > chosen the latest from mine and Olivier's. Please, correct me, if it is > wrong.
I think no fixes line required here, this patch is not fixing a defect, but adding a new support for a pmdinfo tool. I can remove fixes line while applying. Thanks, ferruh > > Andrew. >
