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]

Date:	Wed, 23 Aug 2006 23:11:57 -0500
From:	James Bottomley <James.Bottomley@...elEye.com>
To:	Dax Kelson <dax@...ulabs.com>
Cc:	Greg KH <gregkh@...e.de>, Andrew Morton <akpm@...l.org>,
	Theodore Bullock <tbullock@...tel.com>, robm@...tmail.fm,
	brong@...tmail.fm, erich@...ca.com.tw, greg@...ah.com,
	linux-kernel@...r.kernel.org
Subject: Re: Areca arcmsr kernel integration for 2.6.18?

On Wed, 2006-08-23 at 17:25 -0600, Dax Kelson wrote:
> It would be great if the arcmsr driver could be included in 2.6.18 so it
> can make into all the new distro releases that will be happening the
> last 3-4 months of the year.
> 
> It is completely self contained and it isn't changing any existing code
> (ergo it can't break anything) so I believe there is quite a bit of
> precedence for "late" inclusion in 2.6.18?
> 
> There are lots of users of this hardware (myself included) that would be
> very appreciative.

Well ... really no.  Kernel development isn't about distro releases.
Most of them pull from the upstream git trees anyway, so the problem
shouldn't arise.

There's precedent for putting relatively uncontroversial drivers into
the -rc tree.  However, arcmsr has had a rather difficult path into the
kernel.  Moving it into scsi-misc is a signal that it goes from being
out of tree to in-tree candidate (i.e. I'm happy with the quality now,
but I'll give other people a chance to voice concerns), but on a slow
path that allows people time to find problems and fix them.  This path
also dictates a time line for any final objections arising (i.e. up
until 2.6.18 is declared).

James

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