From: Greg KH <gregkh@suse.de>
To: Andy Gay <andy@andynet.net>
Cc: Roland Dreier <rdreier@cisco.com>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
Ken Brush <kbrush@gmail.com>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH] Airprime driver improvements to allow full speed EvDO transfers
Date: Mon, 3 Jul 2006 11:16:21 -0700 [thread overview]
Message-ID: <20060703181621.GA8448@suse.de> (raw)
In-Reply-To: <1151949329.3285.545.camel@tahini.andynet.net>
On Mon, Jul 03, 2006 at 01:55:28PM -0400, Andy Gay wrote:
> On Mon, 2006-07-03 at 10:00 -0700, Greg KH wrote:
> > Yes, this driver is already split into 2 different ones (look in the
> > recent -mm releases). Sierra wants to have their devices be in their
> > own driver, as the chip is a little different from the other ones. This
> > means that those devices are now controlled by a driver called "sierra"
> > and the other devices still are working with the airprime driver.
> >
> > This should hopefully fix the different endpoint issue, and allow new
> > devices to be supported properly, as Sierra Wireless is now maintaining
> > that driver.
> Aha, good news. So this patch is already obsolete, for the Sierra stuff
> anyway. And as I only have Sierra kit to work with, I reckon I should
> drop out of this now.
No, not at all. I'll gladly add your patch to the sierra driver, if you
say it works for your devices.
> I did make some changes to the last patch to do the cleanup stuff in the
> open function, do you want to see those?
Yes, please send the latest version, and I'll apply it.
thanks,
greg k-h
next prev parent reply other threads:[~2006-07-03 18:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 5:48 [PATCH] Airprime driver improvements to allow full speed EvDO transfers Andy Gay
2006-06-30 7:10 ` Andrew Morton
2006-06-30 8:52 ` Pete Zaitcev
2006-06-30 16:59 ` Andy Gay
2006-06-30 10:51 ` Sergei Organov
2006-06-30 12:13 ` [linux-usb-devel] " Alan Cox
2006-06-30 12:02 ` Arjan van de Ven
2006-06-30 13:34 ` Alan Cox
2006-06-30 16:35 ` Andy Gay
2006-07-07 17:23 ` Sergei Organov
2006-07-07 20:07 ` Alan Cox
2006-07-10 10:36 ` Sergei Organov
2006-07-10 11:10 ` Alan Cox
2006-07-10 15:54 ` Sergei Organov
2006-07-10 17:31 ` Alan Cox
2006-07-10 17:24 ` Sergei Organov
2006-07-13 14:17 ` Sergei Organov
2006-07-13 15:40 ` Alan Cox
2006-07-13 18:20 ` Sergei Organov
2006-07-13 19:08 ` Greg KH
2006-07-14 10:13 ` Sergei Organov
2006-06-30 20:04 ` Roland Dreier
2006-06-30 20:13 ` Andy Gay
2006-07-02 18:48 ` Roland Dreier
2006-07-02 20:29 ` Andy Gay
2006-07-02 20:47 ` Roland Dreier
2006-07-03 7:00 ` Jeremy Fitzhardinge
2006-07-03 14:21 ` Andy Gay
2006-07-03 16:28 ` Jeremy Fitzhardinge
2006-07-03 17:00 ` Andy Gay
2006-07-03 17:00 ` Greg KH
2006-07-03 17:55 ` Andy Gay
2006-07-03 18:08 ` Jeremy Fitzhardinge
2006-07-03 18:16 ` Greg KH [this message]
2006-07-03 22:43 ` Andy Gay
2006-07-03 15:43 ` [linux-usb-devel] " Ken Brush
2006-07-03 16:19 ` Andy Gay
2006-07-11 18:31 ` Sergei Organov
2006-07-11 18:55 ` Andy Gay
2006-07-12 9:20 ` Sergei Organov
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=20060703181621.GA8448@suse.de \
--to=gregkh@suse.de \
--cc=andy@andynet.net \
--cc=jeremy@goop.org \
--cc=kbrush@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=rdreier@cisco.com \
/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