shige@netbsd.org wrote:

> Do you point out how to name kernel configuration file?
> If there is a naming rule for kernel configuration file,
> it's better to apply the rule.

I think there is no strict rule, but many ports have
one GENERIC which has all (or most) features.
Some ports has optional *_TINY or *_SMALL config files.
In this case, you can remove not only optinal devices
but some other options or file-system etc.

arch/evb* ports may require more than one config files
for each board or machine, but I think it's still better
to have only one GENERIC-like kernel for each board,
so that autobuild could check any breakage by building
only one kenrel config, and people who will add or change
MI features could see at least which MD config files
should be updated for their changes.
---
Izumi Tsutsui