On Mon, Oct 10, 2022 at 12:45 PM Bruce Richardson <bruce.richard...@intel.com> wrote: > > To ensure all users are aware of KNI's deprecated status at build time > we can take the following actions: > > 1. disable the library by default. It can be re-enabled by setting > disabled_libs to the empty string (or other string not including > 'kni') > > 2. add support for a list of deprecated libs to the lib/meson.build file > so the error message for KNI being disabled includes the fact that it > is a deprecated library. > > 3. for the dependent NIC driver, drivers/net/kni, modify the driver > build code to similarly flag the deprecation in the reason why > the driver is not being built.. > > NOTE: This is part of the deprecation process for KNI agreed by the DPDK > technical board.[1] > > [1] http://mails.dpdk.org/archives/dev/2022-June/243596.html > > Signed-off-by: Bruce Richardson <bruce.richard...@intel.com> > Signed-off-by: David Marchand <david.march...@redhat.com> > > --- > V3: Incorporate code from David M. to generalise the driver dependency > handling of deprecated libs. > V2: correct dpdk_conf lookup key to RTE_LIB_KNI
Thomas had some last minute offlist comments that I handled (he was asking for introducing the deprecated library handling first, then marking kni as deprecated). I handled it and reworked the patches, the end-result is the same. Series applied, thanks Bruce! -- David Marchand
