Re: [PATCH 1/2] tracing: stop making gpio tracing configurable

["Enrico Weigelt, metux IT consult" <lkml@xxxxxxxxx>]

On 06.04.19 23:06, Uwe Kleine-König wrote:

Hi,

>> why 'default y' is not sufficient ?
> 
> I don't know. The kernels I stumbled over which had that disabled were
> not configured by me. 

hmm, so probably the one who configured it in the first place did it
wrong. but the same could happen w/ any other option.

> There are just too many options you could care about.

Right, this has become pretty complex. One thing I really dislike is the
fact that some options are only reachable when certain others are
enabled before, so sou cant just do echo "CONFIG_FOO=y" >> .config
and hope that this does it. And often, you just wanna switch on some
highlevel feature like networking, but have to configure lots of
other things (nic, phy, ip stack, ...)

I've written a little tool for helping w/ that:

https://github.com/metux/kmct

(I'm planning to integrate it into ptxdist, once I've got some spare
time again ;-)).

> So reducing the number of options is a good direction in my eyes.

Well, depends ;-)

In that specific case, you're probably right (at least I haven't had a
usecase for having trace enabled, but gpio trace disabled, yet). But we
both know that in embedded world we often need to trim down the kernel.

So, ACK for the general idea, but haven't actually tested the patch yet.


--mtx

-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@xxxxxxxxx -- +49-151-27565287