From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH 2.6.17-rc4] I2C: sis96x SMBus quirks cannot
Date: Wed, 24 May 2006 07:57:30 +0000 [thread overview]
Message-ID: <20060524095730.7b4763d2.khali@linux-fr.org> (raw)
In-Reply-To: <20060513182612.GB8642@jupiter.solarsys.private>
Hi Mark,
Sorry for the late reply.
> The sis96x SMBus PCI device depends on the order of two different
> quirks, which depends on link order. But this is apparently not
> guaranteed, as seen on a recent FC4 kernel. This patch fixes the
> quirk so that it works without depending on the link order.
>
> http://lists.lm-sensors.org/pipermail/lm-sensors/2006-April/015962.html
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id\x189719
>
> This code was suggested by Jean Delvare; the patch was tested and
> should be considered for 2.6.17.
I'm happier with this patch than the previous one. However, I'm still
not really comfortable with it. Given that we don't understand why the
quirk order suddenly became untrustworthy, it's hard to justify that we
want this fix in 2.6.17, especially when vanilla kernels are not
affected by the problem as far as I know.
At any rate, this patch does belong to the pci tree and not the i2c
tree, so I am not the one who can push it. Please post this patch on
the linux-pci list and get it discussed there. Hopefully the people
there will be able to explain how the quirks sequencing works.
(Please put me in Cc, I'm interested in the answer.)
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2006-05-24 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 18:26 [lm-sensors] [PATCH 2.6.17-rc4] I2C: sis96x SMBus quirks cannot Mark M. Hoffman
2006-05-24 7:57 ` Jean Delvare [this message]
2006-05-24 10:24 ` Mark M. Hoffman
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=20060524095730.7b4763d2.khali@linux-fr.org \
--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.