On 2016-02-21, Ben Hutchings wrote: >> --- a/debian/installer/armhf/modules/armhf-armmp/mmc-modules >> +++ b/debian/installer/armhf/modules/armhf-armmp/mmc-modules >> @@ -5,4 +5,5 @@ mmci >> omap_hsmmc >> sunxi-mmc >> dw_mmc-exynos >> +dw_mmc-rockchip >> sdhci-bcm2835 > > Would it make sense to replace this list with a wildcard in the default > mmc-modules file: > > drivers/mmc/host/** Overall, I like the idea of using wildcards to include enabled drivers by default, so that drivers for new platforms get automatically included. The only downside I see, is if a driver was accidentally disabled in the config (or due to some new conflicting config), it will happily produce a package without that driver... The obvious advantage is it will likely reduce the number of round-trip bug reports to enable drivers in both the kernel and the udebs, so I'd be supportive of using wildcards for that reason. live well, vagrant
Attachment:
signature.asc
Description: PGP signature