netdev - Re: Steps to integrate new 40G Network driver to the kernel tree

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

Message-ID: <20110621165236.33ae4149@nehalam.ftrdhcpuser.net>
Date:	Tue, 21 Jun 2011 16:52:36 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Joyce Yu - System Software <joyce.yu@...cle.com>
Cc:	netdev@...r.kernel.org
Subject: Re: Steps to integrate new 40G Network driver to the kernel tree

On Tue, 21 Jun 2011 16:47:12 -0700
Joyce Yu - System Software <joyce.yu@...cle.com> wrote:

> 
> Since it is a new driver, shall I follow the "Submitting Drivers for the 
> Linux Kernel" Doc? The driver is ready and passed all our QA cycles. I  
> have three source base, one is for 2.6.16 and 2.6.18 (for RHL 5.X and 
> SLES 10 SP3) , one is for 2.6.32 (For RHL 6.X, SLES11SP1), one for 
> 2.6.27 (For SLES11). Can it be integrated to the 2.6.18 and 2.6.32 tree? 
> or it has to be in the latest 2.6.39 or later?
> 

Do you want the driver to show up in 3.0 (aka 2.6.40) or next release.
For 3.0 submit patch against 3.0-rc4 for next release base the patch
against the network development tree (net-next-2.6).

The code should remove all special case code to deal with old kernel
versions. No backward compatiablity #ifdef's

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