linux-kernel - Re: Areca arcmsr kernel integration for 2.6.18?

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: <20060824165924.GA13807@kroah.com>
Date:	Thu, 24 Aug 2006 09:59:24 -0700
From:	Greg KH <greg@...ah.com>
To:	Theodore Bullock <tbullock@...tel.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Arjan van de Ven <arjan@...radead.org>,
	Dax Kelson <dax@...ulabs.com>, Greg KH <gregkh@...e.de>,
	James Bottomley <James.Bottomley@...elEye.com>,
	Andrew Morton <akpm@...l.org>, robm@...tmail.fm,
	brong@...tmail.fm, erich@...ca.com.tw, linux-kernel@...r.kernel.org
Subject: Re: Areca arcmsr kernel integration for 2.6.18?

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/