From: Rasmus Villemoes > Sent: 10 August 2023 10:09 ... > We really have to stop pretending it's ok to rely on header a.h > automatically pulling in b.h, if a .c file actually uses something > declared in b.h. [Of course, the reality is more complicated; e.g. we > have many cases where one must include linux/foo.h, not asm/foo.h, but > the actual declarations are in the appropriate arch-specific file. > However, we should not rely on linux/bar.h pulling in linux/foo.h.] IMHO (for what it matters) it would be better to focus on why #include <cdev.h> pulls in around 350 other headers (look at a .d file) that worry about moving a few files into a new 'leaf' header from somewhere that pretty much everything has to include anyway. David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
