From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Paul Rolland <rol@as2917.net>
Cc: "'Davide Libenzi'" <davidel@xmailserver.org>,
"'Thomas Winischhofer'" <twini@xfree86.org>,
"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: [patch] SiS IRQ router 96x detection (2.5.69) ...
Date: 22 Jun 2003 12:40:14 +0100 [thread overview]
Message-ID: <1056282008.2070.23.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <00b201c33897$e36378b0$2101a8c0@witbe>
On Sul, 2003-06-22 at 09:25, Paul Rolland wrote:
> Hello,
>
> > didn't work. I did spend a few hours on the patch and I was willing to
> > spend another one to see the kernel fixed. But if he does not
> > care, why
> > should I ?
>
> Maybe because some others *do* appreciate the work you did, and the
> patch being available...
Don't get me wrong - I am glad he's done a lot of detective work on this
and on other stuff. That isn't the only problem however - we have cases
where there are entire ranges of PCI idents that have one driver and
others requiring more care that we dont handle well right now either (eg
440GX).
Another problem is that the table entries get used which means the
table itself cannot be __init.
That makes me wonder if we should in fact have a set of detect functions
that fill in a struct irq_router * and remove most of the array while fixing
the other stuff. That cleans up the detect, removes the 440GX ifdefs properly
with some care, removes the 440GX bios dmi table entries, and fixes SiS.
It isnt that Davide's patch makes it too ugly, its already too ugly, Davide and
also 440GX just hit the places that make it rather obvious it wants a proper
clean up
Alan
prev parent reply other threads:[~2003-06-22 11:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 6:44 Davide Libenzi
2003-06-19 23:36 ` Thomas Winischhofer
2003-06-20 19:14 ` Davide Libenzi
2003-06-21 12:23 ` Alan Cox
2003-06-21 20:49 ` Davide Libenzi
2003-06-22 1:58 ` Thomas Winischhofer
2003-06-22 3:52 ` Davide Libenzi
2003-06-22 8:25 ` Paul Rolland
2003-06-22 11:40 ` Alan Cox [this message]
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=1056282008.2070.23.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@as2917.net \
--cc=twini@xfree86.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
all inboxes | Powered by JetHome®