From: Greg KH <gregkh@suse.de>
To: Dax Kelson <dax@gurulabs.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
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 20:42:46 -0700 [thread overview]
Message-ID: <20060824034246.GA18826@suse.de> (raw)
In-Reply-To: <1156375551.4306.10.camel@mentorng.gurulabs.com>
On Wed, Aug 23, 2006 at 05:25:51PM -0600, Dax Kelson wrote:
> 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.
What distros would that be? And how do you know that they are going to
freeze their kernels at 2.6.18?
> 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?
Then it can easily be bundled as a "kernel module package" for those
same distros if this is the case :)
thanks,
greg k-h
next prev parent reply other threads:[~2006-08-24 3:43 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 [this message]
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
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=20060824034246.GA18826@suse.de \
--to=gregkh@suse.de \
--cc=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=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