On Fri, 21 Jun 2019, Marc Gonzalez wrote: > On 21/06/2019 01:43, Finn Thain wrote: > > > On Thu, 20 Jun 2019, Marc Gonzalez wrote: > > > >> How likely is it that distro kernels would *not* enable CHR_DEV_SG? > >> (Distros tend to enable everything, and then some.) > > > > How likely is it that embedded developers would *not* disable > > CHR_DEV_SG? They tend to disable everything, and then enable only what > > they need. > > I don't see where you're going with this line of reasoning? >
Exactly. This sort of reasoning goes nowhere. > Below is my current (as of next-20190612) defconfig. > > Notice the options marked as "not set". These are options that are > enabled by default (and which I've disabled). > > Everyone thinks "their" option is critical (and it is, *to them*) but, > in fact, few really are -- universally. The relevant policy is documented in Documentation/kbuild/kconfig-language.txt. If there are useful generalizations about the choice of defaults for Kconfig symbols (or changing those defaults) that are not documented then they probably should be. --
