From: Jeff Garzik <jgarzik@pobox.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: PCI Hotplug Drivers for 2.5
Date: Thu, 24 Oct 2002 17:52:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805236@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805223@msgid-missing>
KOCHI, Takayoshi wrote:
>>We need this driver as it's the only solution for DIG64 compliant IPF
>>platforms.
>
>
> No, not for all DIG64 compliant IPF platforms. NEC TX7 is also
> a DIG64 compliant IPF platform but doesn't need your driver.
Tangent:
Intel is wrong by renaming IA64 to "IPF".
It was previously used as "Intel Processor Family". IA64 is a far
better name, and I will continue to use that in preference to IPF.
Re-using an acronym is silly and creates confusion.
Jeff
next prev parent reply other threads:[~2002-10-24 17:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 5:10 [Linux-ia64] Re: PCI Hotplug Drivers for 2.5 Greg KH
2002-10-24 5:59 ` KOCHI, Takayoshi
2002-10-24 6:12 ` Greg KH
2002-10-24 11:49 ` Matthew Wilcox
2002-10-24 14:52 ` Jeff Garzik
2002-10-24 16:24 ` [Linux-ia64] " Lee, Jung-Ik
2002-10-24 16:37 ` Lee, Jung-Ik
2002-10-24 16:46 ` [Linux-ia64] " Greg KH
2002-10-24 16:54 ` Greg KH
2002-10-24 17:39 ` KOCHI, Takayoshi
2002-10-24 17:40 ` [Linux-ia64] " Lee, Jung-Ik
2002-10-24 17:52 ` Jeff Garzik [this message]
2002-10-24 17:59 ` Matthew Wilcox
2002-10-24 18:19 ` Lee, Jung-Ik
2002-10-24 18:39 ` Lee, Jung-Ik
2002-10-24 22:06 ` [Linux-ia64] " Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-10-24 18:19 [Linux-ia64] " Lee, Jung-Ik
2002-10-24 17:40 Lee, Jung-Ik
2002-10-24 17:59 ` [Linux-ia64] " Matthew Wilcox
2002-10-24 4:33 Lee, Jung-Ik
2002-10-24 5:10 ` Greg KH
2002-10-24 5:59 ` KOCHI, Takayoshi
2002-10-24 6:12 ` Greg KH
2002-10-24 11:49 ` [Linux-ia64] " Matthew Wilcox
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=marc-linux-ia64-105590709805236@msgid-missing \
--to=jgarzik@pobox.com \
--cc=linux-ia64@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.