On Mon, Dec 01, 2025 at 10:16:58AM +0000, david laight wrote: > On Mon, 1 Dec 2025 04:50:42 +0200 > Andy Shevchenko <[email protected]> wrote: > > On Sun, Nov 30, 2025 at 11:09:25PM +0000, david laight wrote: > > > On Sun, 30 Nov 2025 21:44:46 +0200 > > > Andy Shevchenko <[email protected]> wrote:
... > > kernel.h elimination (in the form it exists right now) is very fruitful. > > However, you may help with the (say) ioctl.h or whatever you consider > > really fruitful, we all will thank you (no jokes). > > > > This is the first #include path for ioctl.h > > In file included from ../include/asm-generic/ioctl.h:5, > from ./arch/x86/include/generated/uapi/asm/ioctl.h:1, > from ../include/uapi/linux/ioctl.h:5, > from ../include/uapi/linux/random.h:12, > from ../include/linux/random.h:10, > from ../include/linux/nodemask.h:94, > from ../include/linux/numa.h:6, > from ../include/linux/cpumask.h:17, > from ../arch/x86/include/asm/paravirt.h:21, > from ../arch/x86/include/asm/irqflags.h:102, > from ../include/linux/irqflags.h:18, > from ../include/linux/spinlock.h:59, > from ../include/linux/swait.h:7, > from ../include/linux/completion.h:12, > from ../include/linux/crypto.h:15, > from ../arch/x86/kernel/asm-offsets.c:9: > > Get past that and sched.h => processor.h => cpuid/api.h also > gets you to paravirt.h. > I suspect a lot of headers get pulled in like that. And several headers like ioctl.h that is "pull half of everything". device.h, for example. So, you can start untangling them piece by piece. Not sure how [1] is actual right now, but I believe plenty of those can still be used. [1]: https://lwn.net/ml/linux-kernel/[email protected]/ -- With Best Regards, Andy Shevchenko
