Re: [PATCH/RFC] headers: drop 2 #included headers from

* Rasmus Villemoes wrote: > [...] Now I finally got around to writing some scripts for that, so here's a > visualization of (the evolution of) the problem: > > https://wildmoose.dk/header-bloat/ Nice! In particular your final conclusion is impressive and scary: > So the typical (median) tran

Re: [PATCH/RFC] headers: drop 2 #included headers from

On Fri, Feb 16 2018, Ingo Molnar wrote: > * Randy Dunlap wrote: > >> Does anyone know or see why needs or >> ? There are no direct uses in AFAICT. > > These are likely historical, plus it's a classic 'tragedy of the commons' > scenario: it's easy to take away from the "public good" of "clea

Re: [PATCH/RFC] headers: drop 2 #included headers from

* Randy Dunlap wrote: > Does anyone know or see why needs or > ? There are no direct uses in AFAICT. These are likely historical, plus it's a classic 'tragedy of the commons' scenario: it's easy to take away from the "public good" of "clean header dependencies" and very hard to add to it:

[PATCH/RFC] headers: drop 2 #included headers from

From: Randy Dunlap It seems that does not need nor . 8 kernels builds are successful without these 2 headers (allmodconfig, allyesconfig, allnoconfig, and tinyconfig on both i386 and x86_64). is #included 3875 times in 4.16-rc1, so this reduces #include processing of these 2 files by a total