From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Nick Piggin <piggin@cyberone.com.au>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SiS ISA bridge IRQ routing on 2.6 ...
Date: Wed, 29 Oct 2003 23:11:19 +0000 [thread overview]
Message-ID: <1067469078.10526.12.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.56.0310291124230.973@bigblue.dev.mdolabs.com>
On Mer, 2003-10-29 at 19:27, Davide Libenzi wrote:
> Alan did not like my approach, so I'll let him post to Linus his work. If
I generalised it to remove a ton of nasty 440GX hacks and also make the
code smaller by swapping a big table for little __init functions. I sent
akpm comments on it but I never did a 2.6 version directly. Its the same
code in both cases however.
Right now I have exams, which is why I'm reading email not revising ;)
prev parent reply other threads:[~2003-10-29 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 3:45 SiS ISA bridge IRQ routing on 2.6 Davide Libenzi
2003-10-29 4:55 ` Nick Piggin
2003-10-29 19:27 ` Davide Libenzi
2003-10-29 23:11 ` 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=1067469078.10526.12.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).