LKML Archive on
help / color / mirror / Atom feed
From: Greg KH <>
To: Kevin Lloyd <>
Subject: Re: [PATCH] usb-serial: Sierra driver - add devices and update dtr
Date: Thu, 17 Jan 2008 10:04:53 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <3415E2A2AB26944B9159CDB22001004D022577B3@nestea.sierrawireless.local>

On Mon, Jan 14, 2008 at 09:21:32AM -0800, Kevin Lloyd wrote:
> > Hm, no, the intrusion into the driver is just too much this late in
> the
> > release cycle to allow this.
> >
> > Now I will be glad to only add the new device ids for the devices that
> > do not rely on the new changes right now, but that's it.
> >
> > So, right now I have a separate patch split out of your original one
> > that is below.  Should I modify it and not include some of these
> device
> > ids right now?  You mention 0023, is that the only one I should remove
> > from this patch?
> 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?

And is this device even public yet?

> 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).


greg k-h

  reply	other threads:[~2008-01-17 20:57 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 [this message]
2008-01-17 23:15           ` Kevin Lloyd
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).