On Tue, Jul 13, 2021 at 02:16:17PM +0300, Andy Shevchenko wrote: > On Tue, Jul 13, 2021 at 12:37:46PM +0200, Greg Kroah-Hartman wrote: > > On Tue, Jul 13, 2021 at 11:45:41AM +0300, Andy Shevchenko wrote: > > > kernel.h is being used as a dump for all kinds of stuff for a long time. > > > Here is the attempt cleaning it up by splitting out container_of() and > > > typeof_memeber() macros. > > > > That feels messy, why? > > Because the headers in the kernel are messy. Life is messy and can not easily be partitioned into tiny pieces. That way usually ends up being even messier in the end... > > Reading one .h file for these common > > macros/defines is fine, why are container_of and typeof somehow > > deserving of their own .h files? > > It's explained here. There are tons of drivers that includes kernel.h for only > a few or even solely for container_of() macro. And why is that really a problem? kernel.h is in the cache and I would be amazed if splitting this out actually made anything build faster. > > What speedups are you seeing by > > splitting this up? > > C preprocessing. Numbers please. greg k-h
