Subject: Re: Areca arcmsr kernel integration for 2.6.18?
From: Dax Kelson <dax@gurulabs.com>
To: James Bottomley <James.Bottomley@SteelEye.com>, Greg KH <gregkh@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, Theodore Bullock <tbullock@nortel.com>,
       robm@fastmail.fm, brong@fastmail.fm, erich@areca.com.tw, greg@kroah.com,
       linux-kernel@vger.kernel.org
In-Reply-To: <1154530428.3683.0.camel@mulgrave.il.steeleye.com>
References: <00a701c6b2b4$bb564b50$0e00cb0a@robm>
	 <25E284CCA9C9A14B89515B116139A94D0C78805F@zrtphxm0.corp.nortel.com>
	 <20060731200309.bd55c545.akpm@osdl.org>
	 <1154530428.3683.0.camel@mulgrave.il.steeleye.com>
Content-Type: text/plain
Date: Wed, 23 Aug 2006 17:25:51 -0600
Message-Id: <1156375551.4306.10.camel@mentorng.gurulabs.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1051
Lines: 29

On Wed, 2006-08-02 at 10:53 -0400, James Bottomley wrote:
> On Mon, 2006-07-31 at 20:03 -0700, Andrew Morton wrote:
> > > Ok, so how does this go from here into the mainline kernel?
> > 
> > James has moved the driver into the scsi-misc tree, so I assume he has
> > 2.6.19 plans for it.
> 
> Yes, that's the usual path for scsi-misc.
> 
> James

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.

Dax Kelson

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