From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Andrew Chew <achew@nvidia.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.8-rc2] intel8x0.c to include CK804 audio support
Date: Mon, 26 Jul 2004 22:09:11 -0400 [thread overview]
Message-ID: <4105B947.1000106@pobox.com> (raw)
In-Reply-To: <20040726180601.3b88d166.akpm@osdl.org>
Andrew Morton wrote:
> "Andrew Chew" <achew@nvidia.com> wrote:
>
>>I sincerely apologize about the mangled patch. I'll be more careful
>>next time (and check my mailer settings).
>
>
> Is OK - you're in good company ;)
>
>
>>The #ifdef was for consistency (I noticed that there were other IDs
>>similarly defined in intel8x0.c). I don't see why we'd need it, either.
>>We should probably remove PCI_DEVICE_ID_NVIDIA_MCP2_AUDIO and
>>PCI_DEVICE_ID_NVIDIA_MCP3_AUDIO #defines from intel8x0.c as well, as
>>they're similarly redundant. For that matter, why not remove all of the
>>PCI_DEVICE_ID_* #defines from the intel8x0.c driver, and make sure the
>>device IDs are defined in pci_ids.h.
>>
>>Want me to submit a patch for that?
>
>
> Let's leave that up to Jeff.
Jaroslav and the ALSA guys... no idea who maintains the ALSA i810 driver.
In any case, I think the device id constants are a waste, and have
stopped using the *_DEVICE_ID_* constants in my drivers. The vendor id
is generally common across many drivers, but rarely does one care about
sharing arbitrary name<->arbitrary id mappings these days, when one
driver supports so many chips.
Jeff
next prev parent reply other threads:[~2004-07-27 2:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 0:46 [PATCH 2.6.8-rc2] intel8x0.c to include CK804 audio support Andrew Chew
2004-07-27 1:06 ` Andrew Morton
2004-07-27 2:09 ` Jeff Garzik [this message]
2004-07-28 17:30 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2004-07-29 0:13 Andrew Chew
2004-07-29 13:31 ` Takashi Iwai
2004-07-22 2:08 Andrew Chew
2004-07-27 0:38 ` Andrew Morton
2004-07-27 4:27 ` Lee Revell
2004-07-27 4:57 ` Paul Jackson
2004-07-27 6:43 ` Denis Vlasenko
2004-07-27 17:41 ` Lee Revell
2004-07-27 22:05 ` Lee Revell
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=4105B947.1000106@pobox.com \
--to=jgarzik@pobox.com \
--cc=achew@nvidia.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@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.