From: Karsten Keil <keil@b1-systems.de>
To: David Miller <davem@davemloft.net>
Cc: torvalds@linux-foundation.org, lars.ellenberg@linbit.com,
netdev@vger.kernel.org, andreas@eversberg.eu,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ISDN: Add PCI ID for HFC-2S/4S Beronet Card PCIe
Date: Tue, 16 Mar 2010 02:08:57 +0100 [thread overview]
Message-ID: <201003160208.57232.keil@b1-systems.de> (raw)
In-Reply-To: <20100315.160133.67908104.davem@davemloft.net>
On Dienstag, 16. März 2010 00:01:33 David Miller wrote:
> From: Karsten Keil <keil@b1-systems.de>
> Date: Mon, 15 Mar 2010 14:18:41 +0100
>
> > A few subdevice IDs seem to have been dropped when hfc_multi was
> > included upstream, just compare the list at
> > http://www.openvox.cn/viewvc/misdn/trunk/hfc_multi.c?revision=75&view=ann
> >otate#l175 with the IDs in drivers/isdn/hardware/mISDN/hfcmulti.c
> >
> > Added PCIe 2 Port card and LED settings (same as PCI) /KKe
> >
> > Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
> > Signed-off-by: Karsten Keil <keil@b1-systems.de>
>
> We don't add new defines to linux/pci_ids.h, it is deprecated.
> Simply add the device ID constants to the table.
Good policy, makes sense. Will send a new version.
May a check for adding defines to <linux/pci_ids> would help to enforce it.
>
> The only exception is the case where a device ID is used in
> more than one driver, but even that scenerio is heavily
> discouraged.
>
Is here some plan to cleanup drivers for -next and remove IDs from pci_ids.h,
or should it not changed for old entries ?
Karsten
next prev parent reply other threads:[~2010-03-16 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 13:18 [PATCH] ISDN: Add PCI ID for HFC-2S/4S Beronet Card PCIe Karsten Keil
2010-03-15 13:18 ` [PATCH V2] " Karsten Keil
2010-03-16 2:09 ` David Miller
2010-03-15 23:01 ` [PATCH] " David Miller
2010-03-16 1:08 ` Karsten Keil [this message]
2010-03-16 2:06 ` David Miller
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=201003160208.57232.keil@b1-systems.de \
--to=keil@b1-systems.de \
--cc=akpm@linux-foundation.org \
--cc=andreas@eversberg.eu \
--cc=davem@davemloft.net \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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).