netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Joyce Yu - System Software <joyce.yu@oracle.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>, netdev@vger.kernel.org
Subject: Re: Steps to integrate new 40G Network driver to the kernel tree
Date: Wed, 22 Jun 2011 01:14:13 +0100	[thread overview]
Message-ID: <1308701653.3093.113.camel@localhost> (raw)
In-Reply-To: <4E012EF1.3050005@oracle.com>

On Tue, 2011-06-21 at 16:53 -0700, Joyce Yu - System Software 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?

There are 'longterm' branches for Linux 2.6.27 and 2.6.32, but they
don't include new drivers.  If you want your driver to go into existing
distributions then you have to talk to the distributors.  They will
generally tell you that your driver should be accepted in mainline Linux
first.  So you should first submit a driver based on David Miller's
net-2.6 tree (targetting 3.0) or net-next-2.6 (targetting 3.1).

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.


  reply	other threads:[~2011-06-22  0:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15 23:51 Steps to integrate new 40G Network driver to the kernel tree Joyce Yu - System Software
2011-04-16  0:54 ` Stephen Hemminger
     [not found]   ` <4E012D80.4090907@oracle.com>
2011-06-21 23:52     ` Stephen Hemminger
2011-06-21 23:53     ` Joyce Yu - System Software
2011-06-22  0:14       ` Ben Hutchings [this message]
2011-04-16  0:57 ` Ben Hutchings

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1308701653.3093.113.camel@localhost \
    --to=bhutchings@solarflare.com \
    --cc=joyce.yu@oracle.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).