mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Dax Kelson <dax@gurulabs.com>
Cc: Greg KH <gregkh@suse.de>, 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
Subject: Re: Areca arcmsr kernel integration for 2.6.18?
Date: Wed, 23 Aug 2006 23:11:57 -0500	[thread overview]
Message-ID: <1156392717.26289.44.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <1156375551.4306.10.camel@mentorng.gurulabs.com>

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



  parent reply	other threads:[~2006-08-24  4:12 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
2006-08-24  4:11               ` James Bottomley [this message]
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=1156392717.26289.44.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=brong@fastmail.fm \
    --cc=dax@gurulabs.com \
    --cc=erich@areca.com.tw \
    --cc=greg@kroah.com \
    --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

all inboxes | Powered by JetHome®