lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1193232490.3396.10.camel@localhost.localdomain>
Date:	Wed, 24 Oct 2007 09:28:10 -0400
From:	James Bottomley <James.Bottomley@...elEye.com>
To:	David Miller <davem@...emloft.net>
Cc:	jeff@...zik.org, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org, linux-scsi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] final SCSI pieces for the merge window

On Tue, 2007-10-23 at 15:36 -0700, David Miller wrote:
> From: Jeff Garzik <jeff@...zik.org>
> Date: Tue, 23 Oct 2007 18:06:51 -0400
> 
> > James Bottomley wrote:
> > > On Tue, 2007-10-23 at 17:09 -0400, Jeff Garzik wrote:
> > >> James Bottomley wrote:
> > >>> This should be the final SCSI updates; it's mainly just a few accessor
> > >>> completion updates and two driver merges (sym2 and qla2xxx) we also
> > >>> secured DaveM's agreement to remove fcal/fc4, which explains the high
> > >>> removal line count.
> > >>>
> > >>> The patch is available here:
> > >>>
> > >>> master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git
> > >> I guess I have the go-ahead to merge the end-CDROM-polling async 
> > >> notification work you've been repeatedly ignoring?
> > > 
> > > I haven't been ignoring it ... it just needs quite a bit of work; the
> > > best way to accelerate it seems to be simply to do it (add the
> > > supported/trigger event bitmasks and expand the infrastructure).  I just
> > > haven't had the time within the merge window.
> > 
> > James, things cannot get bottlenecked like this.  You have had MONTHS to 
> > say something like this.  The code was ready BEFORE the merge window.
> > 
> > I really think you have the knowledge to be SCSI maintainer, but not the 
> > time.
> 
> Unfortunately, I think this is an important point.
> 
> Developers depend strongly upon a subsystem maintainer to
> "make time" for these things so that work integration does
> not get delayed past the merge window if at all possible.
> 
> Not being able to "make time" to do these things is a great
> way to lose contributers.
> 
> James, whilst there is no doubt in my mind that skill-wise
> you are probably the most capable scsi maintainer, your "lack
> of time" is sounding like a broken record and harming the
> development process.

OK, so it's no secret that I'm the last of the subsystem maintainers
whose day job isn't working on the linux kernel.  If you want a full
time person, who did you have in mind?

James


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ