From: Jeff Garzik <jeff@garzik.org>
To: dougg@torque.net
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] final SCSI pieces for the merge window
Date: Wed, 24 Oct 2007 10:32:50 -0400 [thread overview]
Message-ID: <471F5792.1030000@garzik.org> (raw)
In-Reply-To: <471F104C.5040005@torque.net>
Douglas Gilbert wrote:
> Jeff Garzik wrote:
>> 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.
>
> Jeff,
> If only I had a dollar (Canadian unit please) for
> each day some of my libata patches were queued
> up to you before you accepted them.
>
> Remember MODE SELECT ...
You're darned right, I've screwed up in the past. Sat on stuff "until I
get time to rewrite it" and that sort of thing. My colleagues give me
lumps for it too :)
We talked about this issue at the Kernel Summit -- collectively we need
to stop holding on to useful, working stuff for months on end. It
serves nobody.
We have to rediscover our roots: "release early, release often"
Jeff
next prev parent reply other threads:[~2007-10-24 14:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 20:58 [GIT PATCH] final SCSI pieces for the merge window James Bottomley
2007-10-23 21:09 ` Jeff Garzik
2007-10-23 21:20 ` James Bottomley
2007-10-23 22:06 ` Jeff Garzik
2007-10-23 22:36 ` David Miller
2007-10-24 13:28 ` James Bottomley
2007-10-24 14:27 ` Matthew Wilcox
2007-10-30 13:00 ` Denys Vlasenko
2007-10-24 15:14 ` Andrew Morton
2007-10-24 15:35 ` Linus Torvalds
2007-10-24 19:09 ` Andrew Morton
2007-10-24 9:28 ` Douglas Gilbert
2007-10-24 14:32 ` Jeff Garzik [this message]
2007-10-24 13:24 ` James Bottomley
2007-10-24 14:30 ` Jeff Garzik
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=471F5792.1030000@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@linux-foundation.org \
--cc=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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