From: Henning Schmiedehausen <hps@intermeta.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux IDE Mailingliste <linux-ide@vger.kernel.org>
Subject: Re: PCI Constants Update for SATA Driver
Date: Sun, 27 Feb 2005 21:05:06 +0100 [thread overview]
Message-ID: <1109534706.19325.6.camel@forge.intermeta.de> (raw)
In-Reply-To: <4222250C.6060302@pobox.com>
Let me rephrase:
What sense does it make to have PCI_VENDOR_ID and PCI_DEVICE_ID
constants if using them is optional/discouraged?
Regards
Henning
On Sun, 2005-02-27 at 14:52 -0500, Jeff Garzik wrote:
> Henning Schmiedehausen wrote:
> > Hi Jeff,
> >
> > then what sense does it make to have pci_ids.h at all?
>
> pci_ids.h does not only contain PCI_DEVICE_ID_xxx constants.
>
> Jeff
>
>
>
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development
Linux, Java, perl, Solaris -- Consulting, Training, Engineering
"Now you can start with implementation and integration and do the
requirements later". -- Prof. Dr. Dr. h.c. Manfred Broy about the new
german federal software development standard "V-Model XT"
(found at http://de.biz.yahoo.com/050207/299/4en0t.html)
next prev parent reply other threads:[~2005-02-27 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 17:42 PCI Constants Update for SATA Driver Henning Schmiedehausen
2005-02-27 18:08 ` Jeff Garzik
2005-02-27 19:20 ` Henning Schmiedehausen
2005-02-27 19:52 ` Jeff Garzik
2005-02-27 20:05 ` Henning Schmiedehausen [this message]
2005-02-27 20:07 ` Jeff Garzik
2005-03-02 1:47 ` Benjamin Herrenschmidt
2005-03-02 5:49 ` Jeff Garzik
2005-03-02 1:46 ` Benjamin Herrenschmidt
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=1109534706.19325.6.camel@forge.intermeta.de \
--to=hps@intermeta.de \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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.