netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dhollis@davehollis.com
Cc: bhutchings@solarflare.com, jeff@garzik.org, netdev@vger.kernel.org
Subject: Re: [PATCH - REPOST] asix.c - Add support for AX88772A devices -
Date: Thu, 15 Jan 2009 08:22:53 -0800 (PST)	[thread overview]
Message-ID: <20090115.082253.154478845.davem@davemloft.net> (raw)
In-Reply-To: <1232024974.4105.251.camel@dhollis-lnx>

From: David Hollis <dhollis@davehollis.com>
Date: Thu, 15 Jan 2009 08:09:34 -0500

> On Wed, 2009-01-14 at 16:53 +0000, Ben Hutchings wrote:
> 
> > > @@ -1451,6 +1588,10 @@ static const struct usb_device_id        produc
> > >         // Cables-to-Go USB Ethernet Adapter
> > >         USB_DEVICE(0x0b95, 0x772a),
> > >         .driver_info = (unsigned long) &ax88772_info,
> > > +}, {
> > > +       // ASIX AX88772A
> > > +       USB_DEVICE(0x0b95, 0x772a),
> > > +       .driver_info = (unsigned long) &ax88772a_info,
> > 
> > This is matching the same id as the entry above, so how will it ever be
> > used?  Do the bind operations distinguish them somehow?
> > 
> 
> Ugh!  I didn't notice that either.  Unfortunately, I don't have this new
> device to be able to test with so I have to rely on the vendors
> contribution.  I would presume that the Cables-to-Go device needs to be
> using ax88772a_info and in the current state, it isn't going to.  I'll
> check with the contributor for an assist on that.

Grrr, I just noticed this and I'm ripping this patch out of
my tree.

Sigh.

  reply	other threads:[~2009-01-15 16:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 16:12 [PATCH - REPOST] asix.c - Add support for AX88772A devices - David Hollis
2009-01-14 16:53 ` Ben Hutchings
2009-01-15  5:38   ` David Miller
2009-01-15 13:09   ` David Hollis
2009-01-15 16:22     ` David Miller [this message]
2009-01-15  5:21 ` 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=20090115.082253.154478845.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bhutchings@solarflare.com \
    --cc=dhollis@davehollis.com \
    --cc=jeff@garzik.org \
    --cc=netdev@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 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).