public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Morton <akpm@osdl.org>
Cc: erich <erich@areca.com.tw>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: About ARECA RAID driver for Linux i386/x86-64
Date: Thu, 03 Feb 2005 22:10:28 -0600	[thread overview]
Message-ID: <1107490229.5502.52.camel@mulgrave> (raw)
In-Reply-To: <20050202205141.0c28faf4.akpm@osdl.org>

On Wed, 2005-02-02 at 20:51 -0800, Andrew Morton wrote:
> Well that's a decision which the scsi maintainers will need to make.  Lots
> of current drivers use LINUX_VERSION_CODE, even though we'd prefer they not
> do so.  I don't know what the scsi policy is for new submissions.

Hey ... I have to have a policy now?

The policy generally is that new submissions need to use the latest
versions of the API.  If the driver needs to work on 2.4, it should use
the 2.4 compat layer for 2.6 drivers (and if there's a problem or
something missing, we can update 2.4).

James



  reply	other threads:[~2005-02-04  4:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  4:33 About ARECA RAID driver for Linux i386/x86-64 erich
2005-02-03  4:51 ` Andrew Morton
2005-02-04  4:10   ` James Bottomley [this message]
2005-02-06 14:50 ` Christoph Hellwig
     [not found] <000001c524bc$d3c546a0$0b02a8c0@kw.de>
     [not found] ` <000c01c52626$32bae8d0$9300a8c0@erich2003>
2005-03-11 22:27   ` Andrew Morton
2005-03-11 22:31   ` Andrew Morton
2005-03-12  0:20   ` Andrew Morton
     [not found] <000801c514c7$04ec0030$9300a8c0@erich2003>
2005-02-18 16:10 ` Linux Christoph Hellwig
2005-02-18 19:21   ` Andrew Morton
     [not found] <001001c508d9$d97a17f0$9300a8c0@erich2003>
2005-02-03  2:08 ` Andrew Morton
2005-02-03 10:05   ` Arjan van de Ven
2005-02-06 14:51     ` Christoph Hellwig

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=1107490229.5502.52.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=erich@areca.com.tw \
    --cc=linux-scsi@vger.kernel.org \
    /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