From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Richard Henderson <rth@twiddle.net>
Cc: Jeff Garzik <jgarzik@pobox.com>, Andrew Morton <akpm@osdl.org>,
Dave Jones <davej@redhat.com>, Greg KH <greg@kroah.com>,
chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil>,
Leendert van Doorn <leendert@watson.ibm.com>,
Reiner Sailer <sailer@watson.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] alpha build fixes
Date: Mon, 21 Mar 2005 14:52:10 +0000 [thread overview]
Message-ID: <1111416728.14833.20.camel@localhost.localdomain> (raw)
In-Reply-To: <20050319231116.GA4114@twiddle.net>
On Sad, 2005-03-19 at 23:11, Richard Henderson wrote:
> On Fri, Mar 18, 2005 at 11:34:07PM -0500, Jeff Garzik wrote:
> > +/* TODO: integrate with include/asm-generic/pci.h ? */
> > +static inline int pci_get_legacy_ide_irq(struct pci_dev *dev, int channel)
> > +{
> > + return channel ? 15 : 14;
> > +}
>
> Am I missing something, or is this *only* used by drivers/ide/pci/amd74xx.c?
> Why in the world would we have this much infrastructure for one driver? And
> why not just not compile that one for Alpha, since it'll never be used.
The issue is bigger - it's needed for the CMD controllers on PA-RISC for
example it appears - and anything else where IDE legacy IRQ is wired
oddly.
next prev parent reply other threads:[~2005-03-21 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 4:34 [PATCH] alpha build fixes Jeff Garzik
2005-03-19 23:11 ` Richard Henderson
2005-03-19 23:16 ` Jeff Garzik
2005-03-21 8:05 ` Bartlomiej Zolnierkiewicz
2005-03-21 9:16 ` Ivan Kokshaysky
2005-03-21 9:45 ` Bartlomiej Zolnierkiewicz
2005-03-21 12:27 ` Benjamin Herrenschmidt
2005-03-21 13:53 ` Ivan Kokshaysky
2005-03-21 23:27 ` Benjamin Herrenschmidt
2005-03-21 14:52 ` Alan Cox [this message]
2005-03-21 18:16 ` Richard Henderson
2005-03-21 18:22 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-03-23 13:49 Matthew Wilcox
2007-12-13 9:21 [patch] alpha: " Ivan Kokshaysky
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=1111416728.14833.20.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=chas@cmf.nrl.navy.mil \
--cc=davej@redhat.com \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=leendert@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=sailer@watson.ibm.com \
/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