public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Theodore Bullock <tbullock@nortel.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Arjan van de Ven <arjan@infradead.org>,
	Dax Kelson <dax@gurulabs.com>, Greg KH <gregkh@suse.de>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Andrew Morton <akpm@osdl.org>,
	robm@fastmail.fm, brong@fastmail.fm, erich@areca.com.tw,
	linux-kernel@vger.kernel.org
Subject: Re: Areca arcmsr kernel integration for 2.6.18?
Date: Thu, 24 Aug 2006 09:59:24 -0700	[thread overview]
Message-ID: <20060824165924.GA13807@kroah.com> (raw)
In-Reply-To: <25E284CCA9C9A14B89515B116139A94D0D353411@zrtphxm0.corp.nortel.com>

On Thu, Aug 24, 2006 at 12:21:01PM -0400, Theodore Bullock wrote:
> I posted a feature enchancement request to the Novell bugzilla for the
> 10.2 openSUSE release (currently scheduled for 2.6.18 AFAIK, depends on
> upstream timelines), and the response from Greg was this:
> 
> "If this driver is in the mainline kernel, it will show up in our
> releases, and that's the only way we can accept it at this point in
> time.  We will not backport it to an older kernel version."

Yes, that was my suse engineer side talking.  It has _nothing_ to do
with my community work, please don't mix the two.

> If the driver goes into 2.6.19 this means 8 to 12 months of time before
> our workstations will be supported enough by Novell to start a more
> widespread deployment in the company out of the test lab.  We would
> prefer this driver to be made available earlier, if only to make
> installation more feasible and kernel upgrades possible.

No, you can _always_ have Novell create a stand-alone kernel module
package if you want them to (and can convince them to, you need to speak
with some project managers to get that to happen...)  You can also do
this on your own, as it is very simple to do and support over time.

Even if this driver went into 2.6.18, you would _still_ have the same
situation from Novell, so I do not see how you bring this up has any
relevance here.

And you don't even know what the next SuSE release will base their
kernel on yet, as it hasn't been decided :)

thanks,

greg k-h

  reply	other threads:[~2006-08-24 17:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28 18:07 Areca arcmsr kernel integration Theodore Bullock
2006-07-28 20:27 ` Greg KH
2006-07-29  1:48   ` Bron Gondwana
2006-07-29  2:14     ` Robert Mueller
2006-07-31 21:32       ` Theodore Bullock
2006-08-01  3:03         ` Andrew Morton
2006-08-02 14:53           ` James Bottomley
2006-08-23 23:25             ` Areca arcmsr kernel integration for 2.6.18? Dax Kelson
2006-08-24  0:20               ` Adrian Bunk
2006-08-24  3:42               ` Greg KH
2006-08-24  5:56                 ` Dax Kelson
2006-08-24  8:34                   ` Arjan van de Ven
2006-08-24 11:41                     ` Alan Cox
2006-08-24 16:21                       ` Theodore Bullock
2006-08-24 16:59                         ` Greg KH [this message]
2006-08-24  4:11               ` James Bottomley
2006-08-24  6:34                 ` Dax Kelson
2006-09-29  4:11                   ` Bron Gondwana

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=20060824165924.GA13807@kroah.com \
    --to=greg@kroah.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=brong@fastmail.fm \
    --cc=dax@gurulabs.com \
    --cc=erich@areca.com.tw \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robm@fastmail.fm \
    --cc=tbullock@nortel.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