On Thu, 07 Feb 2008 21:16:43 -0600 James Bottomley <[EMAIL PROTECTED]> wrote:

> On Thu, 2008-02-07 at 18:46 -0800, Andrew Morton wrote:
> > On Thu, 07 Feb 2008 18:56:46 -0600 James Bottomley <[EMAIL PROTECTED]> 
> > wrote:
> > 
> > > Quite a bit of this is fixing things broken previously (the advansys fix
> > > is still pending resolution, but I'll send it as an -rc fix when we have
> > > it).  There's the final elimination of all drivers that are esp based
> > > but don't use the scsi_esp core (that's mostly m68k and alpha).  Plus
> > > the usual bunch of driver updates and the addition of a new enclosure
> > > services driver and the corresponding ULD.
> > 
> > Sob.  Can we please merge "Convert SG from nopage to fault"?  It has been
> > sent three times, the first time was Dec 5 last year and it has thus far
> > received the lead balloon treatment.  Despite my explicit request for
> > consideration last time I sent it
> > 
> > If there is no movement here then I have to carry the moderately intrusive
> > mm-remove-nopage.patch for another N months and we need to watch out for
> > new ->nopage implementations popping up etc.
> 
> I agree ... I've pinged Doug privately, this is publicly.
> Unfortunately, it is an intrusive change and needs testing .. I just
> don't have the tools that do this for SG.  
> 

I keep on forgetting that sg==dougg.

<looks in MAINTAINERS. Shifts blame.>

In fact scsi is the area in which I have the most who-maintains-what
trouble.  I just don't believe what MAINTAINERS says about scsi drivers and
I tend to resort to git-whatchanged to find out who's really doing stuff. 
The number of [EMAIL PROTECTED] makes my head spin and I tend to cc as many
as I can get my hands on.

IOW: some care and attention to the ./MAINTAINERS file would really help
here.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to