From: "erich" <erich@areca.com.tw>
To: Linux Andrew Morton <akpm@osdl.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: About ARECA RAID driver for Linux i386/x86-64
Date: Thu, 3 Feb 2005 12:33:37 +0800 [thread overview]
Message-ID: <003f01c509a9$87913290$9300a8c0@erich2003> (raw)
Hi,Andrew Morton
Thanks for your doing.
ARECA Linux RAID driver need to support old linux kerenel version.
There are a lot of NAS RAID STORAGE SYSTEM development worker still use it
at old linux kernel.
Maybe I need to released one package that as cleanly as look like a Linux
driver :) modern times :( .
Best Regards
Erich Chen
----- Original Message -----
From: "Andrew Morton" <akpm@osdl.org>
To: "erich" <erich@areca.com.tw>
Cc: <linux-scsi@vger.kernel.org>
Sent: Thursday, February 03, 2005 10:08 AM
Subject: Re: About ARECA RAID driver for Linux i386/x86-64
> "erich" <erich@areca.com.tw> wrote:
> >
> > I have contact with Andrew Morton about ARECA RAID Linux scsi driver
release
> > issue.
> > I hope this package is as look like a Linux driver.
>
> No, it doesn't look anything like a Linux driver :(
>
> I fed the patch through scripts/Lindent. There's a copy at
>
http://www.zip.com.au/~akpm/linux/patches/stuff/areca-raid-linux-scsi-driver.patch.
> I'll include it -mm kernels.
>
> From a very quick look, I'd say that the driver needs quite a bit of work:
>
> - Remove Documentation/scsi/arcmsr.txt - none of it is relevant
>
> - Use named structure initialisers:
>
> struct foo bar = {
> .name1 = value1,
> .name2 = value2,
> };
>
> - Remove all the LINUX_VERSION_CODE tests
>
> - The kernel thread stopping/starting stuff is old fashioned. Use the
> kthread API.
>
> - I suspect it is using old-fashioned SCSI APIs too.
>
>
next reply other threads:[~2005-02-03 4:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 4:33 erich [this message]
2005-02-03 4:51 ` About ARECA RAID driver for Linux i386/x86-64 Andrew Morton
2005-02-04 4:10 ` James Bottomley
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='003f01c509a9$87913290$9300a8c0@erich2003' \
--to=erich@areca.com.tw \
--cc=akpm@osdl.org \
--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