netdev - RE: question re: net-2.6 and net-next-2.6 trees re: patch submission

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] [day] [month] [year] [list]

Message-ID: <8F90F944E50427428C60E12A34A309D22FC801D844@carmd-exchmb01.sierrawireless.local>
Date:	Fri, 30 Apr 2010 22:01:08 -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>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: question re: net-2.6 and net-next-2.6 trees re: patch submission


> On 4/30/2010 7:05 PM David Miller wrote:

>>From: Elina Pasheva <epasheva@...rrawireless.com>
>>Date: Fri, 30 Apr 2010 17:53:14 -0700

>> If I submit a new driver to net-2.6 tree (e.g. sierra_net driver that
>> was applied to net-2.6 tree) where do I submit subsequent patches for
>> that driver - net-2.6 tree or net-next-2.6 tree?

>It depends upon the severity of the fix.

>At this stage in the game on the most serious fixes are going
>in, fixes for things that cause crashes and the like.  However
>since a new driver we might be a little bit more lenient since
>changes to a new driver can harm less people.

Thank you, David.

Would you please apply
[PATCH 1/1] net/usb: initiate sync sequence in sierra_net.c driver
 which is a very serious fix and affects the driver's functionality.
Sorry, it was my bad.

I tested this patch  with USB 306.

Thanks,
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