* Grygorii Strashko <grygorii.strashko@xxxxxx> [210205 13:18]: > On 03/02/2021 13:34, Ivan Jelincic wrote: > > Enable the majority of the Netfilter components as loadable modules > > in the omap2plus_defconfig file. ... > > diff --git a/arch/arm/configs/omap2plus_defconfig b/arch/arm/configs/omap2plus_defconfig > > index f250bf1cc022..9847502d2c97 100644 > > --- a/arch/arm/configs/omap2plus_defconfig > > +++ b/arch/arm/configs/omap2plus_defconfig > > @@ -87,6 +87,155 @@ CONFIG_IP_PNP_DHCP=y > > CONFIG_IP_PNP_BOOTP=y > > CONFIG_IP_PNP_RARP=y > > CONFIG_NETFILTER=y > > +CONFIG_NF_CONNTRACK=m > > +CONFIG_NF_LOG_NETDEV=m > > +CONFIG_NF_CONNTRACK_ZONES=y > > +CONFIG_NF_CONNTRACK_EVENTS=y > > +CONFIG_NF_CONNTRACK_TIMEOUT=y > > +CONFIG_NF_CONNTRACK_TIMESTAMP=y > > +CONFIG_NF_CT_NETLINK=m > > [..] > > Do we really want to enable all these not TI specific configs? > The main purpose of omap2plus_defconfig is to enable TI specific HW and HW features and > config options required to tests/demonstrate these features - like support for some networking > HW offloads. Well these are loadable modules. And I'd like to have omap2plus_defconfig and multi_v7_defconfig usable as a base config for distros to use. For built-in options I agree. We should only enable absolute minimum for built-in optoins as otherwise things get even more bloated. Regards, Tony
