Re: Things not referenced in kernel configs, but mentioned in files.*

[John Nemeth <jnemeth%cue.bc.ca@localhost>]

On Nov 12,  3:38pm, coypu%sdf.org@localhost wrote:
} On Mon, Nov 12, 2018 at 10:23:26AM -0500, Greg Troxel wrote:
} > coypu%sdf.org@localhost writes:
} > 
} > > This is an automatically generated list with some hand touchups, feel
} > > free to do whatever with it. I only generated the output.
} > >
} > > ac100ic
} > > acemidi
} > > acpipmtr
} > > [snip]
} > 
} > I wonder if these are candidates to add to an ALL kernel, and if it will
} > turn out that they are mostly not x86 things.
} > 
} > I see we only have ALL for i386/amd64.  I wonder if it makes sense to
} > have one in evbarm.
} 
} The actual search was roughly (and I didn't re-test these commands)
} find src/sys -name 'files.*' | xargs grep 'attach' | awk '{print $2}' > drivers
} for i in `cat drivers`; do echo $i; grep "^$i[^a-z]" src/sys/arch/*/conf/*; done |grep -v ALL > appearances-in-configs
} grep -B 1 '[^0-9]0$' appearances-in-configs > no-appearance-in-configs
} 
} 
} And some manual removal of things that are obviously not drivers,
} removing duplicates, sorting...
} 
} So, I am excluding things that appear in ALL, and I am not checking if
} they appear as modules.
} 
} So far I had complaints about the appearance of 'lm' which cannot be
} safely included in a default kernel, for example.

     wbsio and wt also seems to fit in that category.  Maybe change
the regex to "^#?$i[^a-z]" to catch commented out things.  Of
course, the flip side is that things that are commented out are
naturally going to get less testing.

}-- End of excerpt from coypu%sdf.org@localhost