netdev - RE: [PATCH 1/1] net/usb: initiate sync sequence in sierra

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <8F90F944E50427428C60E12A34A309D22FC801D84A@carmd-exchmb01.sierrawireless.local>
Date:	Sat, 1 May 2010 22:53:52 -0700
From:	Elina Pasheva <epasheva@...rrawireless.com>
To:	David Miller <davem@...emloft.net>
CC:	"dbrownell@...rs.sourceforge.net" <dbrownell@...rs.sourceforge.net>,
	Rory Filer <rfiler@...rraWireless.com>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH 1/1] net/usb: initiate sync sequence in sierra_net.c
 driver


> On Saturday, May 01, 2010 6:08 PM David Miller wrote:

>>From: Elina Pasheva <epasheva@...rrawireless.com>
>>Date: Wed, 28 Apr 2010 16:28:24 -0700

>> Subject: [PATCH 1/1] net/usb: initiate sync sequence in sierra_net.c driver
>> From: Elina Pasheva <epasheva@...rrawireless.com>
>>
>> The following patch adds the initiation of the sync sequence to
>> "sierra_net_bind()". If this step is omitted, the modem will never sync up
>> with the host and it will not be possible to establish a data connection.
>> This is a high priority patch.
>>
>> This patch has been checked against net-2.6 tree.
>> Signed-off-by: Elina Pasheva <epasheva@...rrawireless.com>
>> Signed-off-by: Rory Filer <rfiler@...rrawireless.com>
>> Tested-by: Elina Pasheva <epasheva@...rrawireless.com>

>Applied.

Thank you very much, David!
Elina


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html