From 121cb804be36967d9ec71f07ebee7238d34dc3e7 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Mathieu=20B=C3=A9rard?= Date: Thu, 17 Aug 2006 16:55:41 +0000 Subject: [PATCH] M40 vs. M40X issue hopefully resolved: dmi_matched now return a non null result which means that we stop on the FIRST fully matched entry of omnibook_ids[] which means that we MUST store records in that list from the MORE specific to the LEAST specific. As M40X is now before M40 this sould works. And that was the behaviour of the old (pre fork) DMI matching system and thus the intended one as the list order was not modified. --- init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/init.c b/init.c index 9ff2303..9972186 100644 --- a/init.c +++ b/init.c @@ -98,7 +98,7 @@ static int __init dmi_matched(struct dmi_system_id *dmi) laptop_model = (char*) dmi->ident; else laptop_model = dmi_get_system_info(DMI_PRODUCT_VERSION); - return 0; + return 1; /* return non zero means we stop the parsing selecting this entry*/ } /* -- 2.43.5