mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Klaus S. Madsen" <ubuntu@hjernemadsen.org>
To: maximilian attems <max@stro.at>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Jean Delvare <khali@linux-fr.org>,
	linux-kernel@vger.kernel.org, Chuck Short <zulcss@ubuntu.com>,
	Tim Gardner <tim.gardner@canonical.com>
Subject: Re: [PATCH] hdaps add support for various IBM thinkpads R61/T61/T61P
Date: Fri, 13 Jun 2008 14:45:43 +0200	[thread overview]
Message-ID: <20080613124543.GK30713@42.dk> (raw)
In-Reply-To: <20080613122751.GF7212@baikonur.stro.at>

On Fri, Jun 13, 2008 at 14:27:51 +0200, maximilian attems wrote:
> On Fri, Jun 13, 2008 at 01:40:02PM +0200, Klaus S. Madsen wrote:
> > On Fri, Jun 13, 2008 at 13:26:47 +0200, maximilian attems wrote:
> > > diff --git a/drivers/hwmon/hdaps.c b/drivers/hwmon/hdaps.c
> > > index 26df06f..e07c712 100644
> > > --- a/drivers/hwmon/hdaps.c
> > > +++ b/drivers/hwmon/hdaps.c
> > > @@ -515,6 +515,7 @@ static struct dmi_system_id __initdata hdaps_whitelist[] = {
> > >  	HDAPS_DMI_MATCH_NORMAL("IBM", "ThinkPad R50"),
> > >  	HDAPS_DMI_MATCH_NORMAL("IBM", "ThinkPad R51"),
> > >  	HDAPS_DMI_MATCH_NORMAL("IBM", "ThinkPad R52"),
> > > +	HDAPS_DMI_MATCH_NORMAL("IBM", "ThinkPad R61"),
> > >  	HDAPS_DMI_MATCH_INVERT("LENOVO", "ThinkPad R61i"),
> > >  	HDAPS_DMI_MATCH_INVERT("IBM", "ThinkPad T41p"),
> > >  	HDAPS_DMI_MATCH_NORMAL("IBM", "ThinkPad T41"),
> > > @@ -523,6 +524,8 @@ static struct dmi_system_id __initdata hdaps_whitelist[] = {
> > >  	HDAPS_DMI_MATCH_NORMAL("IBM", "ThinkPad T43"),
> > >  	HDAPS_DMI_MATCH_INVERT("LENOVO", "ThinkPad T60"),
> > >  	HDAPS_DMI_MATCH_INVERT("LENOVO", "ThinkPad T61"),
> > > +	HDAPS_DMI_MATCH_NORMAL("IBM", "ThinkPad T61"),
> > > +	HDAPS_DMI_MATCH_NORMAL("IBM", "ThinkPad T61P"),
> > I would suspect that this part of the patch is unnecessary. It would be
> > strange if there are any T61's where the manufacturer is IBM, instead of
> > LENOVO, since the T60 is older and has the manufacturer listed as
> > LENOVO, and no entry exists for IBM.
> > 
> > But according to the comment at the top of the struct, the second line
> > (the T61P part) is unnecessary, as a T61p already would be matched by
> > the T61 line. 
> 
> according to hardy git there is no bug reference, but the T61p got added
> before the T61 both by chuck. could you enlighten us please on the T61
> IBM match need? 
I believe that this patch is a response to
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/133636

But as I stated in that bug description, the fix did not work for me.
Also both R61, T60, T61 and T61p owners responded that their
dmi-manufacturer was listed as LENOVO. So I'm quite dubious if these
entries will match any machines at all?

-- 
Kind regards,
	Klaus S. Madsen

  reply	other threads:[~2008-06-13 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 11:26 maximilian attems
2008-06-13 11:40 ` Klaus S. Madsen
2008-06-13 12:27   ` maximilian attems
2008-06-13 12:45     ` Klaus S. Madsen [this message]
2008-06-13 13:21       ` Jean Delvare
2008-06-13 13:21       ` maximilian attems

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=20080613124543.GK30713@42.dk \
    --to=ubuntu@hjernemadsen.org \
    --cc=akpm@linux-foundation.org \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@stro.at \
    --cc=tim.gardner@canonical.com \
    --cc=zulcss@ubuntu.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®