All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Theodore Bullock" <tbullock@nortel.com>,
	James Bottomley <James.Bottomley@steeleye.com>
Cc: robm@fastmail.fm, brong@fastmail.fm, erich@areca.com.tw,
	greg@kroah.com, dax@gurulabs.com, linux-kernel@vger.kernel.org
Subject: Re: Areca arcmsr kernel integration
Date: Mon, 31 Jul 2006 20:03:09 -0700	[thread overview]
Message-ID: <20060731200309.bd55c545.akpm@osdl.org> (raw)
In-Reply-To: <25E284CCA9C9A14B89515B116139A94D0C78805F@zrtphxm0.corp.nortel.com>

On Mon, 31 Jul 2006 17:32:07 -0400
"Theodore Bullock" <tbullock@nortel.com> wrote:

> 
> >I believe these final issues have already been fixed:
> 
> 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.

  reply	other threads:[~2006-08-01  3:03 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 [this message]
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
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=20060731200309.bd55c545.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=James.Bottomley@steeleye.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.