I assumed he was referring to just dropping those fields of they didn't make sense for the architecture. That would make sense to do.
Andi Kleen <a...@linux.intel.com> wrote: >> - the module aliases host tool has no arch specific dependencies at >> all except having x86cpu as one of the entries: would you mind >> dropping the x86 prefix there? Or rather add dependencies on $ARCH? >> (If we drop it there, we basically end up with 'cpu:' everywhere) > >Should be fine. > >> - in the vendor/family/model case, it may be preferable to drop these >> fields entirely from certain modules' aliases if they match on 'any' >> (provided that the module tools permit this) rather than add >> architecture, variant, revision, etc fields for all architectures if >> they can only ever match on one > >The module tools require everything matching with the same wild cards. > >So I don't know how "any" would work. > >-Andi -- Sent from my mobile phone. Please pardon brevity and lack of formatting. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
