Re: _KERNEL_OPT and 0x6e074def

2023-12-19 Thread Jason Thorpe
> On Dec 19, 2023, at 10:33 AM, Jason Thorpe wrote: > > >> On Dec 19, 2023, at 10:01 AM, Edgar Fuß wrote: >> >> 0x6e074def > > the-ripe-vessel:thorpej 99$ grep UNDEFINED * > mkheaders.c:#define UNDEFINED ('n' << 24 | 0 << 20 | 't' << 12 | 0xdefU) > mkheaders.c:/* Value for defined

Re: _KERNEL_OPT and 0x6e074def

2023-12-19 Thread Jason Thorpe
> On Dec 19, 2023, at 10:01 AM, Edgar Fuß wrote: > > 0x6e074def the-ripe-vessel:thorpej 99$ grep UNDEFINED * mkheaders.c:#define UNDEFINED ('n' << 24 | 0 << 20 | 't' << 12 | 0xdefU) mkheaders.c:/* Value for defined options with value UNDEFINED */ mkheaders.c: return (unsigned int)(h !=

Re: _KERNEL_OPT and 0x6e074def

2023-12-19 Thread Paul Goyette
On Tue, 19 Dec 2023, Edgar Fu? wrote: What's the point of #include'ing opt_foobar.h only if _KERNEL_OPT is defined and what's magic about 0x6e074def? The opt_* files only exist when building a kernel. They do not exist when building loadable modules. In the module case, any options needed

_KERNEL_OPT and 0x6e074def

2023-12-19 Thread Edgar Fuß
What's the point of #include'ing opt_foobar.h only if _KERNEL_OPT is defined and what's magic about 0x6e074def?