linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi@vger.kernel.org, Christoph Hellwig <hch@infradead.org>,
	achim_leubner@adaptec.com,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/4] more gdth patches for your amusement
Date: Mon, 24 Sep 2007 20:25:28 -0400	[thread overview]
Message-ID: <46F85578.70503@garzik.org> (raw)
In-Reply-To: <1189865576.3339.0.camel@localhost.localdomain>

James Bottomley wrote:
> On Sat, 2007-07-21 at 16:34 -0400, Jeff Garzik wrote:
>> This is the rest of the stuff checked into the 'gdth' branch of
>> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git
>>
>> As noted before, I'm fine with Christoph's gdth work superceding mine,
>> or whatever.  This was just me poking around.  Hopefully the patches
>> are useful for illustration, if nothing else.
>>
>> 1) [SCSI] gdth: kill gdth_{read,write}[bwl] wrappers
>> 2) [SCSI] gdth: Move probe-time error handling code to end of each function
>> 3) [SCSI] gdth: make some virt ctrlr code common; shuffle SHT members
>> 4) [SCSI] gdth: convert to modern SCSI host alloc/scan
> 
> OK, we've had these competing patch sets floating around for two months
> now.  Christoph and Jeff, can we get agreement on which is going in?

Well, my opinion is

1) When judging by total amount of positive improvement, Christoph's 
patches are superior -- he has more overall cleanups than I do.

2) When judging by likelihood of inducing breakage, I feel my changes 
are superior.  My gdth changes tightly adhere to the 
equivalent-transformation method of shuffing code around, enabling 
further improvements.  IOW, I resisted the urge to make cleanups and fix 
insignificant, pre-existing bugs during the transformations.

3) I am utterly unmotivated to merge the two patchsets.  Someone should 
make an executive decision, pull one patchset, and drop the other.  My 
coding "mood" has swung from cleaning up code to writing new SAS drivers :)

	Jeff



  reply	other threads:[~2007-09-25  0:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21 20:34 [PATCH 0/4] more gdth patches for your amusement Jeff Garzik
2007-07-21 20:34 ` [PATCH 1/4] gdth: kill gdth_{read,write}[bwl] wrappers Jeff Garzik
2007-07-21 20:35 ` [PATCH 2/4] gdth: Move probe-time error handling code to end of each function Jeff Garzik
2007-07-21 20:35 ` [PATCH 3/4] gdth: make some virt ctrlr code common; shuffle SHT members Jeff Garzik
2007-07-21 20:36 ` [PATCH 4/4] gdth: convert to modern SCSI host alloc/scan Jeff Garzik
2007-07-21 20:38 ` [PATCH 0/4] more gdth patches for your amusement Jeff Garzik
2007-09-15 14:12 ` James Bottomley
2007-09-25  0:25   ` Jeff Garzik [this message]
2007-09-25  8:20     ` Christoph Hellwig
2007-09-25  9:51       ` Boaz Harrosh
2007-09-25 11:56         ` Matthew Wilcox
2007-09-25 12:17           ` Boaz Harrosh
2007-09-25 12:22             ` Matthew Wilcox

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=46F85578.70503@garzik.org \
    --to=jeff@garzik.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=achim_leubner@adaptec.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).