We still have the site-local/Kconfig case, so not sure if I can get rid of this entirely. I split off the addition of the osource usage into another CL to see if that makes the linter happy.

Ah, `site-local`... Is that the only one? I guess that could
also be solved easily by creating an empty file there if none
exists?

I'm just wondering if it's worth the hassle to retrofit
`osource`. But, that's your call.

View Change

To view, visit change 48677. To unsubscribe, or for help writing mail filters, visit settings.