LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Kevin Lloyd" <klloyd@sierrawireless.com>
To: "Greg KH" <gregkh@suse.de>
Cc: <linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>,
	<linux-usb-devel@lists.sourceforge.net>
Subject: RE: [PATCH] usb-serial: Sierra driver - add devices and update dtr
Date: Thu, 17 Jan 2008 15:15:23 -0800	[thread overview]
Message-ID: <3415E2A2AB26944B9159CDB22001004D02296DC3@nestea.sierrawireless.local> (raw)
In-Reply-To: <20080117180453.GA7780@suse.de>

> > Correct, the 0x0023 is the only newly added device that requires the
new
> > features.
>
> Does that mean things will not work for this device if it is added to
> the device table, without the code updates?
Adding the device will not break the driver (assuming you remove the
tag).

> And is this device even public yet?

No, but we are trying to add native support for devices into kernels
well 
before they are released in an effort give better native support to
end-users.

> > When do you expect the other changes will be propagated to the
kernel?
> > Would it be in a 2.6.24.x point release or will they have to wait
until
> > 2.6.25?
>
> They will have to wait until 2.6.25, they are too big to go into
2.6.24
> (we are in severe bug-fix mode only right now for .24).
Darn.

Thanks,
 -Kevin


  reply	other threads:[~2008-01-17 23:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10 19:11 [PATCH] usb-serial: Sierra driver - add devices and update dtr Kevin Lloyd
2008-01-10 19:54 ` Greg KH
2008-01-11 17:24   ` Kevin Lloyd
2008-01-11 21:02     ` Greg KH
2008-01-14 17:21       ` Kevin Lloyd
2008-01-17 18:04         ` Greg KH
2008-01-17 23:15           ` Kevin Lloyd [this message]
2008-01-19  0:35             ` Greg KH

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=3415E2A2AB26944B9159CDB22001004D02296DC3@nestea.sierrawireless.local \
    --to=klloyd@sierrawireless.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=linux-usb@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).