From: Alan <alan@lxorguk.ukuu.org.uk>
To: Tejun Heo <htejun@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: regarding VIA quirk fix
Date: Fri, 17 Nov 2006 14:09:31 +0000 [thread overview]
Message-ID: <20061117140931.2657fe0e@localhost.localdomain> (raw)
In-Reply-To: <455D8B44.2060600@gmail.com>
On Fri, 17 Nov 2006 19:13:24 +0900
Tejun Heo <htejun@gmail.com> wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=7415
>
> Any ideas how to proceed on this bug?
The report appears to be about the earlier patch not the one I did from
reading it. That said I don't see it matters which.
The only way to track down any remaining ones is to go line by line
through the PCI configuration and understand what we or the bios mixed up
so its pretty tedious but doable assuming the bug isn't in the SATA
driver in the first place. The IRQ routing on the later chips is pretty
rigid so its not too hard to spot a misconfiguration.
Alan
next prev parent reply other threads:[~2006-11-17 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 10:13 regarding VIA quirk fix Tejun Heo
2006-11-17 14:09 ` Alan [this message]
2006-11-17 17:56 ` Daniel Drake
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=20061117140931.2657fe0e@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=htejun@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox