On Fri, May 1, 2015 at 9:31 PM, Paul Bolle <[email protected]> wrote: > Valentin Rothberg schreef op wo 29-04-2015 om 16:58 [+0200]: >> Sometimes a user might be interested to filter certain reports (e.g., >> the many defconfigs). > > Is this actually useful outside of filtering out defconfigs?
It's a regex, so we can filter entire paths as well (e.g., -i 'arch/.*' to ignore all issues in arch/). Until now, I only used it to get rid of all the defconfigs. >> Now, this can be achieved by specifying a Python >> regex with -i / --ignore. > > Patch hijack: it's been my view for some time now that almost all > defconfigs are outdated in one way or another. And they are outdated > because they are not, as far as I can tell, updated regularly. So I > wonder whether there are any guidelines for defconfigs. What is their > purpose? What exactly can one expect when using a defconfig? > As far as I know, it's really hard to manually configure certain boards. With defconfigs, only few people have to go through the fire. Two years ago I tried to manually select a kernel configuration for my Nexus 7 and failed desperately since some feature constraints are just not visible/understandable from the menu. Not that I am an ARM developer, but there I understood the need to have a defconfig : ) Kind regards, Valentin > Paul Bolle > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
