netdev - Re: [PATCH] usb-net/pegasus: fix pegasus carrier detection

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: <58298.85.91.128.158.1177436881.squirrel@nucleusys.com>
Date:	Tue, 24 Apr 2007 20:48:01 +0300 (EEST)
From:	petkan@...leusys.com
To:	"Greg KH" <greg@...ah.com>
Cc:	"Jeff Garzik" <jeff@...zik.org>, "Dan Williams" <dcbw@...hat.com>,
	"Petko Manolov" <petkan@...leusys.com>, netdev@...r.kernel.org
Subject: Re: [PATCH] usb-net/pegasus: fix pegasus carrier detection

> On Tue, Apr 24, 2007 at 12:49:12PM -0400, Jeff Garzik wrote:
>>  Long term, Greg seemed OK with moving the net drivers from
>> drivers/usb/net
>>  to drivers/usb/net, in line with the current policy of placing net
>> drivers
>>  in drivers/net/*, bus agnostic.  After that move, sending to netdev and
>> me
>>  (as you did here) would be the preferred avenue.
>
> Speaking of which, do you want me to do this in the 2.6.22-rc1
> timeframe?  Usually big code moves like this are good to do right after
> rc1 comes out as the major churn is usually completed then.

Sorry to interfere, but could you guys wait until tomorrow before applying
the patch to your respective GIT trees?  I'd like to check if the code is
doing the right thing and avoid patch reversal.

cheers,
Petko

-
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