From: Petko Manolov <petkan-nPnTwAqkgEqakBO8gow8eQ@public.gmane.org>
To: Oliver Neukum <oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
Cc: Stefan Bader
<stefan.bader-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
petkan-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] Adding blacklist support to the pegasus driver
Date: Tue, 25 Mar 2008 22:44:13 +0200 (EET) [thread overview]
Message-ID: <alpine.DEB.1.10.0803252242550.3288@bender.nucleusys.com> (raw)
In-Reply-To: <200803252135.29249.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 896 bytes --]
On Tue, 25 Mar 2008, Oliver Neukum wrote:
> Am Dienstag, 25. März 2008 21:05:31 schrieb Petko Manolov:
>> On Mon, 24 Mar 2008, Oliver Neukum wrote:
>>
>>> Am Montag 24 März 2008 schrieb Stefan Bader:
>>>> I have been working on a problem which arose from the fact that (at
>>>> least one vendor) some vendors use the same vendor and model number for
>>>> different pieces of hardware.
>>>
>>> That issue can be solved with using the correct macros for probing that
>>> include a device class check.
>>
>> Can you show a driver that is already doing that. I am sorry to be so
>> lazy, but i can't help it... :-)
>
> http://fixunix.com/kernel/256881-add-infamous-huawei-e220-option-c-3.html
>
> Just ask and you shall be answered.
Ah, now i see. :-)
This (if works) seems simpler and more elegant. I'll play with it in the
morning. Thanks for the link.
Petko
prev parent reply other threads:[~2008-03-25 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 16:10 [PATCH] Adding blacklist support to the pegasus driver Stefan Bader
[not found] ` <47E7D266.8050500-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2008-03-24 16:47 ` Oliver Neukum
2008-03-25 20:05 ` Petko Manolov
2008-03-25 20:35 ` Oliver Neukum
[not found] ` <200803252135.29249.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2008-03-25 20:44 ` Petko Manolov [this message]
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=alpine.DEB.1.10.0803252242550.3288@bender.nucleusys.com \
--to=petkan-npntwaqkgeqakbo8gow8eq@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org \
--cc=petkan-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=stefan.bader-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.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.