Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756621AbZLFM2V (ORCPT ); Sun, 6 Dec 2009 07:28:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756298AbZLFM2U (ORCPT ); Sun, 6 Dec 2009 07:28:20 -0500 Received: from smtprelay04.ispgateway.de ([80.67.31.38]:57491 "EHLO smtprelay04.ispgateway.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754575AbZLFM2T (ORCPT ); Sun, 6 Dec 2009 07:28:19 -0500 X-Greylist: delayed 90558 seconds by postgrey-1.27 at vger.kernel.org; Sun, 06 Dec 2009 07:28:19 EST References: <2a6e8c0d0912052133v3e112bdbx2c95b17437bdd182@mail.gmail.com> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Peter Feuerer To: Ian =?UTF-8?B?RS4=?= Morgan Cc: LKML Subject: Re: acerhdf: BIOS product mismatch due to whitespace Date: Sun, 06 Dec 2009 13:28:23 +0100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Df-Sender: 404094 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 988 Lines: 32 Ian E. Morgan writes: > Peter, > > Having just upgraded my AOA150 to 2.6.32, acerhdf was complaining: > > acerhdf: Acer Aspire One Fan driver, v.0.5.18 > acerhdf: unknown (unsupported) BIOS version Acer/AOA150 > /v0.3310, please report, aborting! > > DMI reports the product as "AOA150 " (i.e. 9 spaces after the > 6-character model name). This causes the product match to fail, so I > had to use force_product="AOA150". > > acerhdf: Acer Aspire One Fan driver, v.0.5.18 > acerhdf: forcing BIOS product: AOA150 > > Then all was happy again. Any chance you could strip leading/trailing > whitespace in the product match to avoid this issue? Hi Ian, thanks for reporting, will take care about this issue. kind regards, --peter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/