public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "erich" <erich@areca.com.tw>
To: "James Bottomley" <James.Bottomley@SteelEye.com>
Cc: "Andrew Morton" <akpm@osdl.org>,
	"\"Robert Mueller\"" <robm@fastmail.fm>,
	<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<dax@gurulabs.com>, <brong@fastmail.fm>, <hch@infradead.org>,
	<rdunlap@xenotime.net>
Subject: Re: Areca driver recap + status
Date: Tue, 27 Jun 2006 17:47:47 +0800	[thread overview]
Message-ID: <003701c699ce$c126b550$b100a8c0@erich2003> (raw)
In-Reply-To: 1151333338.2673.4.camel@mulgrave.il.steeleye.com

Dear Robert Mueller,

Does arcmsr still has more than one value per file issue on it?
Maybe I am miss-understand the means of one value per file.
Please tell me the issue, thanks.
About the BE platform, Areca's user on linux sparc platform had ran this 
driver successfuly.
But I attempt to install linux system on ppc platform and run this driver 
for more long time testing this day.
I will patch PAE issue on pci_map_single again and handle SYNCHRONIZE_CACHE 
for your request.

Best Regards
Erich Chen
----- Original Message ----- 
From: "James Bottomley" <James.Bottomley@SteelEye.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: <rdunlap@xenotime.net>; <hch@infradead.org>; <erich@areca.com.tw>; 
<brong@fastmail.fm>; <dax@gurulabs.com>; <linux-kernel@vger.kernel.org>; 
<linux-scsi@vger.kernel.org>; "Robert Mueller" <robm@fastmail.fm>
Sent: Monday, June 26, 2006 10:48 PM
Subject: Re: Areca driver recap + status


> On Wed, 2006-06-21 at 22:28 -0700, Andrew Morton wrote:
>> On Thu, 22 Jun 2006 14:18:23 +1000
>> "Robert Mueller" <robm@fastmail.fm> wrote:
>>
>> > The driver went into 2.6.11-rc3-mm1 here:
>> > http://marc.theaimsgroup.com/?l=linux-kernel&m=110754432622498&w=2
>>
>> One and a half years.
>>
>> Would the world end if we just merged the dang thing?
>
> Not the world perhaps, but I'm unwilling to concede that if a driver
> author is given a list of major issues and does nothing, then the driver
> should go in after everyone gets impatient.
>
> The rules for inclusion are elastic and include broad leeway for good
> behaviour, but this would stretch the elasticity way beyond breaking
> point.
>
> The list of issues is here:
>
> http://marc.theaimsgroup.com/?l=linux-scsi&m=114556263632510
>
> Most of the serious stuff is fixed with the exception of:
>
> - sysfs has more than one value per file
> - BE platform support
> - PAE (cast of dma_addr_t to unsigned long) issues.
> - SYNCHRONIZE_CACHE is ignored.  This is wrong.  The sync cache in the
> shutdown notifier isn't sufficient.
>
> At least the sysfs files have to be fixed before it goes in ... unless
> you want to be lynched by Greg?
>
> What I could do is set up a holding tree for all the fixed ... but -mm
> is doing a good job of that at the moment.
>
> James
>
> 


  parent reply	other threads:[~2006-06-27  9:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22  4:18 Areca driver recap + status Robert Mueller
2006-06-22  5:28 ` Andrew Morton
2006-06-22  6:35   ` Jeff Garzik
2006-06-26 14:48   ` James Bottomley
2006-06-26 15:01     ` Andrew Morton
2006-07-07  8:41       ` erich
2006-07-07  9:04         ` Andrew Morton
2006-06-26 22:32     ` Robert Mueller
2006-06-27 15:27       ` James Bottomley
2006-06-27 15:51         ` Alan Cox
2006-06-27 15:39           ` James Bottomley
2006-06-27 16:36             ` Alan Cox
2006-06-27  0:23     ` Dax Kelson
2006-06-27 15:27       ` James Bottomley
2006-06-27  9:47     ` erich [this message]
2006-06-27 16:12       ` James Bottomley

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='003701c699ce$c126b550$b100a8c0@erich2003' \
    --to=erich@areca.com.tw \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=brong@fastmail.fm \
    --cc=dax@gurulabs.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=robm@fastmail.fm \
    /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