> Date: Tue, 26 Mar 2024 17:08:24 +0000 > From: Gibson Pilconis <gibson...@protonmail.com> > > If it was exclusively accessible within the kernel I'd agree that it > probably isn't neccessary, the trouble is that it is also accessible > by userland programs. pcidump is an example of a userland program > that is part of the OpenBSD project and includes the header, and > that file acts as a reference implantation of sorts for any program > that needs to discover PCI devices. > > Notwithstanding that, if all it takes to avoid potential confusion > and wasted time among developers is a one line include statement, > does the header file having limited uses within the kernel really > make it not worth doing? > > > I'll even fix it myself and submit a patch. I'd just hate to see > this quirk be neither remedied nor documented in some form. > > > Let me know what you guys think though.
It is not a public header and it is just fine as-is for it suse with the kernel and pcidump.
