From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] abituguru3: Please send .. to the abituguru3 (see
Date: Mon, 20 Oct 2008 06:48:26 +0000 [thread overview]
Message-ID: <20081020084826.3aac3b53@hyperion.delvare> (raw)
In-Reply-To: <alpine.DEB.1.10.0810191251550.19058@p34.internal.lan>
Hi Alistair,
On Sun, 19 Oct 2008 20:53:26 +0100, Alistair John Strachan wrote:
> On Sunday 19 October 2008 17:54:15 Justin Piszcz wrote:
> > Kernel: 2.6.27.2:
> > [ 10.242065] abituguru3: found Abit uGuru3, motherboard ID: 0016
> > [ 10.242105] abituguru3: this motherboard was not detected using DMI.
> > Please send the output of "dmidecode" to the abituguru3 maintainer(see
> > MAINTAINERS)
> >
> > Motherboard: AW9D-MAX as shown below.
> >
> > DMI Decode:
> [snip]
> > Product Name: AW9D-MAX (Intel i975-ICH7)
>
> The spaces are a somewhat worrying (Abit haven't done this on other boards I
> have DMI information for), but assuming they're constant through all BIOS
> revisions the attached patch should be safe.
>
> (In the longer term it might be safer to only match the board product name,
> and ignore the chipset information. I'll do this if the need arises.)
I would indeed suggest doing this. It's easy (just use strncmp()
instead of strcmp()) and then you no longer need to pay attention to the
number of spaces in the middle of the string.
> Please test the attached patch. I'll resubmit a cleaned up version if you can
> verify that the kernel message disappears and your sensors still work.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2008-10-20 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 16:54 [lm-sensors] abituguru3: Please send .. to the abituguru3 (see Justin Piszcz
2008-10-19 19:53 ` Alistair John Strachan
2008-10-20 6:48 ` Jean Delvare [this message]
2008-10-20 15:10 ` Justin Piszcz
2008-10-20 16:24 ` Alistair John Strachan
2008-10-20 18:14 ` Justin Piszcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081020084826.3aac3b53@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.