From: Jean Delvare <khali@linux-fr.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, Greg KH <greg@kroah.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: One more Asus SMBus quirk
Date: Tue, 8 Mar 2005 23:21:00 +0100 [thread overview]
Message-ID: <20050308232100.6a9248f2.khali@linux-fr.org> (raw)
In-Reply-To: <422E24A8.4070504@tmr.com>
Hi Bill,
> > [PATCH] PCI: One more Asus SMBus quirk
> >
> > One more Asus laptop requiring the SMBus quirk (W1N model).
>
> Hopefully this and the double-free patch will be included in
> 2.6.11.n+1? They seem to fit the "real bug" criteria.
I see nothing critical in this patch. It gives access to a chip. Without
the patch you cannot access the chip, and that's about it. No bug there,
only a missing feature.
Can't speak for the "double-free patch", don't know what it is all
about.
--
Jean Delvare
next prev parent reply other threads:[~2005-03-08 22:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11099696382684@kroah.com>
2005-03-04 20:53 ` PCI: remove pci_find_device usage from pci sysfs code Greg KH
2005-03-04 20:53 ` [PATCH] PCI: Apple PCI IDs update Greg KH
2005-03-04 20:53 ` [PATCH] PCI: tone down pci=routeirq message Greg KH
2005-03-04 20:53 ` [PATCH] PCI: fix hotplug double free Greg KH
2005-03-04 20:53 ` [PATCH] PCI: One more Asus SMBus quirk Greg KH
2005-03-08 22:18 ` Bill Davidsen
2005-03-08 22:21 ` Jean Delvare [this message]
2005-03-08 22:21 ` Bill Davidsen
2005-03-08 23:37 ` Greg KH
2005-03-09 16:06 ` Bill Davidsen
2005-03-09 16:37 ` Greg KH
2005-03-10 11:54 ` Bill Davidsen
2005-03-10 16:36 ` Greg KH
2005-03-20 14:53 ` PCI: remove pci_find_device usage from pci sysfs code Rolf Eike Beer
2005-03-21 18:40 ` Greg KH
2005-03-24 21:06 ` Rolf Eike Beer
2005-03-28 23:21 ` Greg KH
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=20050308232100.6a9248f2.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=davidsen@tmr.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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
Powered by JetHome