linux-kernel - Re: [PATCH] usb-serial: Sierra driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Jan 2008 11:54:03 -0800
From:	Greg KH <gregkh@...e.de>
To:	Kevin Lloyd <klloyd@...rrawireless.com>
Cc:	linux-kernel@...r.kernel.org, linux@...rrawireless.com,
	linux-usb@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net
Subject: Re: [PATCH] usb-serial: Sierra driver - add devices and update dtr

On Thu, Jan 10, 2008 at 11:11:04AM -0800, Kevin Lloyd wrote:
> From: Kevin Lloyd <linux@...rrawireless.com>
> 
> This patch is targeted for the 2.6.24-rc7 kernel.
> 
> The following improvements were made:
>  - Added new product support: MC5725, AC 880 U, MP 3G (UMTS & CDMA)
>  - Fixed control line issue where asserting DTR on ep5 would close ep2
>  - Added support for calc_num_ports (will help support future composite devices)
> 
> This also covers the devices added by j@....net and
> agilmore@...elessbeehive.com since their patches were not committed to
> the 2.6.23-rc7 kernel.

Those device ids are already in my tree, as it was my understanding that
you would not be sending me patches for them :)

I'll split this patch up into something that updates the device ids and
then does all of the other changes.  The device ids can go into 2.6.24
(and -stable if I miss the merge window), but the other changes should
wait until 2.6.25.

Any objection to this?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/