mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Dax Kelson <dax@gurulabs.com>
Cc: Andrew Morton <akpm@osdl.org>,
	rdunlap@xenotime.net, hch@infradead.org, erich@areca.com.tw,
	brong@fastmail.fm, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org, Robert Mueller <robm@fastmail.fm>
Subject: Re: Areca driver recap + status
Date: Tue, 27 Jun 2006 10:27:49 -0500	[thread overview]
Message-ID: <1151422069.3340.23.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <1151367789.2935.23.camel@mentorng.gurulabs.com>

On Mon, 2006-06-26 at 18:23 -0600, Dax Kelson wrote:
> On Mon, 2006-06-26 at 09:48 -0500, James Bottomley wrote:
> > 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.
> 
> That isn't accurate or fair. Erich has submitted large patches to
> address issues. That hardly qualifies as "does nothing".

Yes, that was unfair, and I apologise for it.  However ...

> > 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?
> 
> Thanks for the new list. Erich has been eager to get work on any
> remaining blockers.

This isn't a new list.  It's extracted from the old list summary of
serious issues which an inspection of the driver reveals to be still
unresolved.  The original list was posted on 20 April

http://marc.theaimsgroup.com/?l=linux-scsi&m=114556263632510

And that one was an redux of a previously posed list that I can't be
bothered to find.

> It would have been nice to have gotten it back on May 19th, they might
> have been resolved by now.
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=114801926400287&w=2

Well, this is what's adding to the rising frustration ... there's
apparently been another hiatus where I thought someone was working on
the rest of the issues labelled serious and no-one was.

James



  reply	other threads:[~2006-06-27 15:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22  4:18 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 [this message]
2006-06-27  9:47     ` erich
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=1151422069.3340.23.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=brong@fastmail.fm \
    --cc=dax@gurulabs.com \
    --cc=erich@areca.com.tw \
    --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

all inboxes | Powered by JetHome®